This is the real explanation. Couple that with a push in the late 90s/early 2000s to roll out high-speed unmetered internet in the form of ADSL and later fiber.

Iceland runs plenty of these and has a nice culture of frequenting the public bathhouse. It’s one of the few things you can do that is actually affordable there.

They do have the advantage of having essentially infinite clean energy in the form of geothermal heat. As do Japan in many cases, for that matter. I’m sure that has something to do with these institutions having staying power there.

Anyway, I think this idea has merits, but not as an energy saving measure. The reason for this is that in order to maintain good water quality, you have to shower thoroughly before getting into the bath, negating the potential energy benefits of the initiative. We can bring it back for it being nice, though!

TRAINS

Testing in prod is a power move honestly. Rock star-level

Kotlin-style async is pretty neat, ngl.

Podcasts often dynamically generate ads at the point of download, making the SponsorBlock-approach unviable: since the media is expected to be variable-length you can’t store media positions that map to advertisement segments.

Healthcare is pretty rough, I’d be willing to bet that the grass actually is greener in this case.

Yes

You can’t deny that it correctly predicted the most likely token in this case.

Yeah, they don’t care that senior talent left because that was the whole point.

What’s wrong with multiple returns?

Agreed to the part about job security being terrible in the U.S, but it’s worth mentioning that the premium you get in income for living in for example San Francisco far outweighs the cost of housing.

• General purpose LLMs are starting to replace everyday queries I used to posit to Google. Perplexity can be quite good for this.
• Copilot as enhanced autocomplete when writing code. A particularly good use-case is writing tests: with a few test cases already written, a sufficiently good test name will most often generate a well-written test case.
• LLMs for lazy generation of SQL queries can sometimes be quite nice.
• Writing assistance for things I find myself struggling to get written by myself. A writing unblocking tool, if you will.

It’s reducing the effort and time I have to put into some things, and I appreciate that. It’s far from perfect, but it doesn’t have to be perfect to be useful.

Realistically I think it’s probably easier to acquire a botnet of less secure systems. This was a targeted attack.

The root cause is the supply not keeping up with demand. Any proposed solution that does not include building like mad is ultimately going to fall short.

Can’t you just walk out the staffed checkout aisles without a receipt, or are they receipt-gated too?

You upload the binary to the App Store, and as a part of the release process they may inspect the binary to figure out what it’s doing.

They of course don’t do that for everything as it’s a bit complicated to do for everything, but it can be an effective means to for example figure out when an app is calling an API in a prohibited manner.

1.8B was the fine they got for anticompetitive behaviour with regards to Apple Music, which is not an insignificant amount for that business unit.

The fines for DMA-violations go up to 10% of global revenue for first-time violations and 20% of global revenue for repeat violations. I would love to see Apple continue fucking around and letting Apple find out in the form of a fine of that magnitude. It would be so damn sweet.

The former.

Absolutely. I think it helps a lot to understand the mechanics of git and rebasing, but after a few times it just makes more sense than merging, really.

I like Yerba Mate, but I dare not drink it that much on account of the absolutely massive caffeine content it has (granted you drink it bombilla-style).

Sorry to hear that. Hope your condition improves, anxiety is a really nasty thing to deal with.

True. I can’t drink unlimited quantities of coffee without having negative effects, as such I limit myself to two cups a day, one in the morning and one after lunch.

Drug addiction is only negative if it causes you problems in life, and I’d say that coffee doesn’t really cause me problems in life.

Nasty thing to say on account of the author of the article being the OP as well.

The fact that you have to kind of understand how git works under the hood to really unlock its full potential is a definite design flaw of the tool, but given its ubiquitous use in our industry, I encourage you to check out how git works under the hood. Once you learn the underlying concepts, you reach a whole new level of proficiency with git, no longer having to just get by, and instead you get to thrive.

I disagree wholeheartedly with this. I consider the commit history as documentation for pull requests and for future history, and as such I make liberal use of interactive rebasing to curate my commits.

Rebasing in general is one of those things that I picked up fairly late, but now it’s essential to my git workflow.

What about Ruff? I’ve been having a great time with Ruff.

I honestly almost golf my code nowadays and just let the tooling fix formatting for me. The space bar and enter key are in an ideal world vestigial for the purposes of programming.

Probably basically all operational expenses, with a minority being cloud expenditure and a majority being salaries for employees, if I had to guess.

I’m assuming that spez gets most of his pay in the form of stock options which doesn’t really cost the company anything real.

Why would there be any fraud? His salary is approved by the board that represents the current shareholders.

It’s also not particularly surprising on account of there being plenty of VC-subsidised companies that never turned a profit, had high salaries for their executives and then IPO’d.

If your question is moreso on the absurdities of capitalism, then that’s another discussion entirely, but I feel it’s important to note that this is nothing out of the ordinary.

The right tool for the right job. I use both, depending on what task I have.

This goes for most things in tech - there’s no one best language, there’s only really a best language for any given job.

Based on their FAQ, they are not shooting for widespread adoption yet. Extension support and multi-platform appears to be on the roadmap.

Fwiw, I like a lot of the ideas behind the editor, and long-term I might consider it a viable option for some of my work.

I have a personal theory that a lot of complaints about working in-person go away when you remove very long commutes, in particular by car.

A bit like how most complaints about pull requests go away if you make it a priority to get them done as fast as possible.

Taking the time to learn how git works on a conceptual level and then how to resolve merge conflicts effectively is a worthwhile investment. Highly recommended

git config --global pull.rebase true

This doesn’t actually read as serious TypeScript, moreso as someone trying to showcase unhinged code.

I’d be happy to be proven wrong with a link to the source code so that I can look the beast in the eye.

So you’re probably not going to be able to swing getting a project greenlit to test everything on your frontend, partly because your management seems a bit stingy, and partly because it’s probably not the best approach to do this kind of thing anyway.

To the claim of that you can’t test UI: only if you’re not creative enough. Behavior can 100% be tested, and is worthwhile to test, while UI looks can be verified with screenshot tests.

How I would probably approach this would be:

1. Get some very basic test execution infrastructure in place. Ideally it runs in CI, but if you have to do it in the dark, then just make sure you can run it locally
2. Try to refactor parts of the code you touch to actually have its behavior testable - do this as a part of any ongoing work of navigating the codebase
3. Whenever you add functionality, add a test to verify it. Write the test first if you can
4. Whenever you encounter a bug, write a test asserting the behavior you want, then fix the bug such that the test gets green.

Following these steps should successively put the codebase into a healthier state.

Another perhaps even more valid option would be to look for a better job - working in headwind from management is not recommended, as it will deteriorate your mental health.

Good luck!

All apps send telemetry

Hilariously untrue statement.

That’s easy to know, actually. Spotify pays 70% of revenue to rights holders, and keeps 30%. Hence an increase of $1 will mean $0.30 for Spotify, and $0.70 to rights holders.

https://labelgrid.com/blog/royalties/spotify-pay-per-stream/