How many of you actually use the headphone jack on your phone?
varsock @ varsock @programming.dev Posts 8Comments 106Joined 2 yr. ago
varsock @ varsock @programming.dev
Posts
8
Comments
106
Joined
2 yr. ago
The statement is very informative. The bug happens under increased read/write operations to the same file causing a race condition.
I also found interesting:
Despite the bug being present in OpenZFS for many years, this issue has not been found to impact any TrueNAS systems. The bug fix is scheduled to be included in OpenZFS 2.2.2 within the next week
I'd really want to know what's driving them
likely ego
This is interesting. Don't have an opinion on it yet.
I wonder what effect this will have on developers' code reuse practices and how it comes across in the interview.
At work I often look at my previous work for how to do boilerplate stuff. And in my recent interview experience I had more opportunities to use the internet and other examples. Very practical
I would appretiate if someone could explain the practical utility of snippets because it just dawned on me how useful they might be.
The letter is a post on his own blog . Hard to distill into a summary so I recommend reading it get more context. But it seems to have boiled down to:
- How It Was:
- Strong adherence to the "don't be evil" ethos, focusing on societal good over profits.
- Open, transparent communication and decision-making processes.
- High morale, with a culture of learning from successes and failures.
- Work focused on benefitting the web and users, rather than Google's immediate interests.
- Collaboration and lack of internal silos, encouraging innovation and autonomy.
- How It Is Now:
- Shift from user-centric to Google-centric, and then to individual-centric decision making.
- Eroded transparency and increase in organizational silos.
- Decline in morale and a culture of distrust between employees and management.
- Focus on short-term financial gains leading to layoffs and defensive employee behavior.
- Lack of clear vision and leadership, resulting in confused and ineffective management.
- Overall deterioration of Google's unique, innovative culture and values.
I've actually found his blog where he talks about this "optimistic merge"
There is a very effective approach (34:00), that big companies like cloudflare use, to ship a product in a fast and quality way. It bears parallels to what you are describing. In essence engineers should not get hung up in the details to trying to solve everything.
- Just build a proof of concept
- Discard the prototype no matter what and start from scratch keeping the initial feedback in mind
- Build something internally that you yourself will use
- Only once something is good enough and is used internally, then release it to beta.
So that tedious process in trying to flush out all the details before seeing a product (or open source effort) working end to end, might be premature before having the full picture.
Brave has superior fingerprint protection, they achieve this by randomizing the browsers fingerprint. Visit EFF's cover your tracks to test your browser.
To achieve the same functionality that brave achieves out of the box with Firefox I need many extensions and then when I profile both browsers, Firefox is more resource intensive. Brave's blocking is native to the browser. I will give Firefox the W because I've read that uBlock is technically more capable. But as a long time Firefox/uBlock user who switched to brave - this has not been noticable.
As for accessibility, I can configure brave to be really aggressive at ad blocking, tracking blocking, fingerprint blocking, and restricting JS even, and all those options I can set from one place instead of in different settings/extensions. When a website breaks, I click on the button next to the URL and immediately have options to granularly dial down the "protection" or add a website to my trusted list. In Firefox I was annoyed to having go through settings for the extension.
Brave plans to continue supporting Manifest V2 after Google kills it. For Ungoogled Chromium, however, it's still undecided, likely depending on whether UG contributors are willing to maintain it.
Brave has superior fingerprint protection, they achieve this by randomizing the browsers fingerprint. Visit EFF's cover your tracks to test your browser.
To achieve the same functionality that brave achieves out of the box with Firefox I need many extensions and then when I profile both browsers, Firefox is more resource intensive. Brave's blocking is native to the browser. I will give Firefox the W because I've read that uBlock is technically more capable. But as a long time Firefox/uBlock user who switched to brave - this has not been noticable.
As for accessibility, I can configure brave to be really aggressive at ad blocking, tracking blocking, fingerprint blocking, and restricting JS even, and all those options I can set from one place instead of in different settings/extensions. When a website breaks, I click on the button next to the URL and immediately have options to granularly dial down the "protection" or add a website to my trusted list. In Firefox I was annoyed to having go through settings for the extension.
Brave plans to continue supporting Manifest V2 after Google kills it. For Ungoogled Chromium, however, it's still undecided, likely depending on whether UG contributors are willing to maintain it.
society gains nothing by preventing a software developer from implementing ...
I see the point you are trying to make but I respectfully disagree. Technology is at the core of seemingly every field and at the core of technology is software. Will it result in direct bodily harm? Rarely. But indirectly the impact is certainly more substantial.
Take internet as an example. The significance of internet and information sharing cannot be disputed. Disturptions to information sharing can send ripples through services that provide essential services. Networking these days is accomplished Vida software defined networking techniques. And we are becoming more dependant on technology and automation.
I can see why the indirect risk is not as scary as direct risk, but you have to admit, as automation is growing and decisions are being made for us, regulation of those that build these systems should not be overlooked. Professional engineers have a code of ethics they have to adhere to and if you read through it you can see the value it would bring.
As a counter example to your "doctors are licensed to not kill people" - orthodontists, who move teeth around, pose no fatal risk to their patients. Should they be exempt from being licensed?
EDIT:
Just yesterday news was published by Reuters that Musk and managers at Tesla knew about defects of autopilot but marketed otherwise. If those working on it had been licensed, then negligence and decietfulness could line them up to lose their license and prevent them from working in this line again. It would bring accountability
good question. Software and computer practices are changing much faster than other fields but with time, pillars are being better and better defined. Production quality code, CI/CD, DevOps, etc..
Civil engieers have a successful licensure process established. See my comment regarding that.
But an approach where a candidate would spend time under a "licensed professional software eng" would favor practical work experience over academic.
the trades is a great example of having to work under a professional. Other engineering disciplines also have successful licensure processes. See my comment regarding that.
There are parallels to be drawn between licensed professionals (like doctors, CPAs, lawyers, civil engineers) that they all have time under a professional and the professional then signs off and bears some responsibility vouching for a trainee.
I think it's important to check for competencies that are valuable to the employer during the interview process. However many, but admittingly not all, employers will use time constrained college level puzzels that a candidate can usually only solve if they have seen it before.
I've been on both sides of the interview process. In my day to day I use a debugger to verify and step through code all the time. Hacker rank, the leading platform to test candidates and generate a metric report, doesn't even have a debugger. Off-by-one index mistakes are sooo common to see from a candidate who is under time pressure. A few iterations with a debugger and problem solved. I advocate for candidates to develop on their on env and share their screen or bring it with them. But anyway, I'm ranting.
I agree with most comments arguing against a standardization and pointing to the weakness. I didn't say it works great, I just wish it was like some other professionals have. See my comment about other engineering disciplines that have a successful licensure process.
I agree with what you said, it is a shit show. but I wish it weren't so.
My good friend is a civil engineer and for him to obtain a Professional Engineer license (PE) he had to complete a four-year college degree, work under a PE licensed engineer for at least four years, pass two intensive competency exams and earn a license from their state's licensure board. Then, to retain their licenses, PEs must continually maintain and improve their skills throughout their careers.
This licencing approach is prohibitive to just "pay your way" through. This never caught on in software and computer eng because of how quickly it was (and still is) changing. But certain pillars are becoming better defined such as CI/CD, production-safe code & practices, DevOps.
to add to this, id like standardization of qualification and competencies - kind of like a license so I don't have to "demonstrate" myself during interviews.
I hate being in a candidate pool that all have a degree and experience, we all go through a grueling interview process on college basics, and the "best one gets picked." Company says "our interview process works great, look at the great candidates we hire." like, duh, your candidate pool was already full of qualified engineers with degrees/experience, what did you expect to happen?
using the settings you described ( minus the VPN ) I was not able to cloak myself over the past several days
Yes, some guy was streaming live on YouTube talking about a subject that he does not otherwise have, and he showed that before talking about the subject, there were no ads for dog toys, and after talking about dogs, there were ads about dog toys. The video isn't really that great because he goes and clicks on an ad about a dog toy and proceeds to get more of them, so he kind of tainted his results.
I wish I didn't waste my time watching this video
7 visits with brave, 7 times identified as the same. I'm using the default options of a fresh brave install
how did you have such success?
thanks for the masterclass in CF tunnels.
I am ready to accept everything you've said but there is the SSH case that keeps tripping me up. For reference, here is the CF docs on Connecting SSH through CF Tunnels.
Can you help me clear up the misunderstanding here? From the docs it appears you can create a SSH key pair on a client and then copy the public key to the server. It does not appear that the docs state you need to share those keys with CF, so I assume (perhaps incorrectly) that my session will be encrypted with my private key (on client) and public key (on server).
Again, what you said appears to make sense, perhaps SSH is the only edge case that is implemented differently?
If you look at which company (apple) and the time of removal of headphone jack (around the time their wireless buds were announced), you'll notice they removed choice so the consumer can only buy more expensive wireless buds, or many many dongles.
The "save space" is an absolute lie. The international (EU, Asia, etc) version of the iPhone has a dedicated SIM card tray. The US model? No tray, just a freakin placeholder where the international version has the SIM tray. Yes, there is a volume of space that can fit 2 headphone jacks on the US iPhone that is just empty.
Look at this iFixit video where they call apple out on it. The placeholder is huge. at ~1:17+