IMO an engineer should be able to develop a complex system which an entire company could potentially be based upon.

A developer who isn’t an engineer would focus more on individual libraries, apps or tools that don’t necessarily require the mindset of an engineer to design and maintain.

Pro tip: If your code gets flogged by git, you can always get revenge with git reflog 😉

Solidarity to our Swedish comrades, showing Tesla the power of united labour!

Hiding under a huge pile of Beans 😂

They’re talking about the rendering speed, not the playback speed.

The text is just completely incorrect in this case. “Hold your finger” doesn’t in any way instruct the user to use the fingerprint scanner so the developer shouldn’t be surprised that its not understood.

I’ve got a MYLR and the sustained acceleration is terrifying, its very seldom that I floor it.

The M3P must be bonkers since its lighter, lower and more powerful.

Yes, the Model Y is the best selling car in Norway ever, but your smooth brain knows much better than everyone who has been in the market and purchased one because it was the best option for them.

Presumably because it uses LFP battery cells? If that’s the case, then the lower rated range is not as important since those cells tolerate many charge cycles to 100%.

One typically only charges to 80% with other Li battery chemistries so one effectively loses that top 20% of range.

Programmers are probably chill af, looks like a very bad day for some network people though.

Only if it’s specified and documented as part of a contract with the user. If they’re relying on internal implementation details, well that’s a good lesson for them not too do that.

There are some massive intrinsic advantages of the CLI though, that apply for everyone, not just leetcoders:

• The terminal can remember everything you ever did. Forgotten the command you wrote 2 months ago? You can do a search for it with a tool like fzfand run the exact same command again.
• Communicating with others. GUI programs require step by step instructions, often accompanied by screenshots while CLI may be copy/pasted.
• Combining programs together. There are a few different techniques for combining CLI programs to search/format output, use secrets without ever having them in the clipboard or on disk, monitor something frequently/constantly etc etc

So while I agree with you that there’s plently of elitism around the CLI, you do yourself a disservice if you try to avoid it.

Thank fuck! I’m so sick of rebasing and merging Dependabot PRs.

Because then when someone else suggests the same thing you can say that its in the backlog 😉

This is the way 🤝

IMO it’s good to have a “shadow backlog” for stuff like this. Keep the actual backlog for prioritised product work, “ideas” and tech debt can be kept in GitHub Issues or even just a wiki page somewhere.

Sexist rubbish

Gradle is absolute rubbish, definitely the worst experience I’ve had with a build system. But Maven is also rubbish.

IMO a CLI should be the primary way of interacting with the build system (see e.g. Go, Rust, JS with NPM or Yarn, Python with Poetry) and manually editing the build file should be reserved for edge cases and extensions.

Wow what a great video, wish it was longer!

Hmmm, I’m not diagnosed but the number of things that are familiar to me is… impressive 🙃

Wait, can people actually work at an even pace?!

Great post! We solve far too many problems (many of them are very much in the nice-to-have category) with our systems at my work, the systems get huge and difficult to change or maintain. I’m on a constant campaign to stop people building things we don’t need, I’m definitely filling my senior role lol.

EAFP vs LBYL

Nice summary, I’ll link confused normie friends to it.

BTW, the header on your site is very large on Firefox mobile

The enshittification doubles by the day, good lord

If you’re really keen on a FOSS setup you may need to go terminal based, I haven’t tried this setup but it looks good

https://www.youtube.com/watch?v=mh_EJhH49Ms