I feel like this is a lost-in-translation problem. Say a new version of something comes out - a library, a framework, whatever - and the devleoper/team shows you the default use. Then another someone comes around and shows their specific use case which might be different than the default - and a bunch of people start parroting that without fully understanding it, for some reason only remembering that it's better than the default.

Seconding the notion that this is not burnout.

But yeah, whenever what you mention happens it's usually a sign that I have to take my lunch break or an afternoon nap.

Yeah, no shit.

I also sometimes stumble upon seemingly very simple things. In such cases I usually open a scratchpad that lets me see values on the fly and start playing around either until I fully understand what's up or until I stop caring (so that I have to redo the process the next time).

But yeah, I get your point. I do develop some sense of those things with enough practice. When I was starting out, I was almost afraid of for example map and reduce, now I like them quite a lot because they let me do things with single expressions instead of with explicit loops.

It's not supposed to be blue as far as I know. You might wanna see a doctor.

If they decided to throw all the fancy stuff in, then yeah, I feel you. Otherwise I'd have to disagree - depending on how you set it up, it can be pretty non-intrusive.

@CaptainRant Not sure if you can patent a set of features.

Is it all that hard to set a pre-commit hook?

I was considering an iPod in the times even before the Classic was called that because of its storage; there were plenty of flash-based players out there that were 1 or 2 gigs at most whereas that particular iPod was 40, 60, 80, even 160 (and the very few HDD-based players from other brands had problems). Never actually managed to get one because at that time they were not officially sold where I am and importing one was ridiculously expensive. So that would've been the only Apple device I would've owned.

Nowadays I have my own Navidrome instance and I'm listening on my phone through a Bluetooth receiver and wired IEMs. Ideally I'd want wired, but it's not worth it - given how noisy it usually is outside, the difference in quality is probably not perceivable.

Regarding battery - yeah, the more things you throw at a single device, the faster you will drain it. But how many dedicated devices do you carry around? Do you always have a camera on you for example?

No, I don't.

@netikras Yeah, as if from then on dude will be immune from existential questions like "Did I really want kids?"...

Hope those folks have sense of humour.

Cinema is also content.

@Lensflare I feel like this is where passphrases came around. From security perspective they're the same as passwords, but from user perspective they might be better.

I think what you're describing is not a problem with working remotely in general but with that specific company.

You shouldn't have to use your own devices - besides maybe peripherals (if you wish) and so on. If they want you to test an app on a device, they should provide the device. Fake camera blur should be fine for calls. On-call duty should be paid on top of the base salary - both stand-by time and active duty.

Ew, row stagger.

Yes. That. 100% that.

Throw out the "clever" shorthands and all the "cool" tricks you've learned. Things need to be as simple and as short as possible while still being readable.

Haven't seen anything break because of tabs. Not saying it's not possible, just that I haven't seen it - and on that matter I'd be curious to see an example.

What I like about tabs is that you can customise how wide they appear without changing the codebase, which you can't do with spaces.

@retoor Maybe people just don't care that much.

I was wondering why it didn't install on my new phone when I was supposed to get everything back.

At least it's not a big deal - the mobile site is almost identical in functionality.

I had all four of mine removed in past year or two. Sometimes it doesn't make sense to keep them. My dentist explained to me that they get demineralised and thus rot way easier than usual, so after the second time I was there to have a cavity fixed, he suggested I just pull them out. And I'm not in the US, I think I only pay like 30 bucks for each one.

It's a bit weird at first, but you get used to it fast. Be prepared for a few days of pain and itchiness though.

IMO many of those would be still useful even without the pitfalls of JS. I very much like things like Omit, Required, Optional, Exclude and so on that let you manipulate types on the fly.

I don't know about the dance, but it's a bit weird that "salsa" also means "sauce".

Glad you're fine.

I think it's good to make habits to check that everything is turned off the last time you're in the kitchen for the day. I for example shut off the propane valve at the bottle even if the stove itself will cut off the flow when no flame is present.

As long as the status codes are correct, I see no problem whatsoever; I'd argue that it's even better than a boring generic page.

Is this happening during making things or during their use afterwards? If it's the former, sounds like someone suggested they should wear gloves and they ignored it; if it's the latter, it's like the material is not well engineered for general use.

... and if you still care about the audio being lossless, FLAC is your friend.

@lorentz Haven't heard of that, but it doesn't make a lot of sense either. Trying to integrate a whole external app (that's probably not meant for that) sounds like all sorts of things waiting to blow up. Instead, integrating just the command line seems to work - VSCode does that, the JetBrains IDEs do that, and for stuff like vim/emacs I guess it's just about either emulating the command line through the editor or opening a non-editor pane because stuff is already running in a terminal...

For me it works - my prompt and all my command line tools are the same as anywhere else (with just a few keybinds being different because I need them in VSCode), and I rarely ever need to see more than two panes at once (for which vertical tiling works well). The "bonus" is that I don't need to switch context to another window or monitor.

... or just that you really don't care what you're listening to.