883 karma · joined May 19, 2013
Then react came along and all developed learning web development after react had little to no knowledge of the platform. They were taught that touching the DOM was a bad thing to do.
That’s about it. Even now when I advocate for vanilla css I get the side eye and “tailwind and shadcn should be the default”. I get it, it’s what most people are familiar with, even if it’s worse than the platform.
I'm an iOS 18 holdout, any chance of a backwards compatible app?
The next CEO of Apple is someone that cares about quality. (As evidenced by how good the hardware is)
Running shoes are converging on two designs: maximalist shoes with a long foam and a narrow foot, or “barefoot” shoes. Which means it’s harder than ever to find something that fits if neither of those work well for you.
That’s not new by any means. It’s no different than zoom installing a native audio plugin for the os, or other software creating files on the system.
Agents should be calling one level of abstraction higher.
Eg calling a function to “find me relevant events in this city according to this users preferences” instead of “list all events in this city”.
There’s a lot more photos now, most of them mediocre, but some exceptional.
It does become harder to filter great photography from noise.
By the time a race engineer is communicating with a driver all of that has been shaken out. Specific concrete options are given to the driver, and usually only one.
Its not bigotry nor is it clever. It’s just word play.
It does have slightly more complexity than I’d like, but most of the design decisions are sound and the code is easy to read.
The best practices engineering influencers shill are geared towards shipping a todo list quickly, and no thought is given towards maintainability.
That is to say, if you target "readable to the majority of engineers with 3-4 years of experience, without them getting confused" then you've hit the mark.
Unless something has changed, it's worse than that. Plugins have unrestricted access to any file on your machine.
When I brought this up in discord a while back they brushed it aside.
With hooks you still need to think about lifecycle, side effects, and state, but the syntax changes.
The real solution is overall application design and thinking through architecture, but unfortunately that’s higher effort than “just use hooks bro”.
The tools are going to get better, and it’s going to lift everyone while doing so. But it will vary across task.
The bottom tier of engineers will have improvements to their code.
The top engineers will move faster. Top engineers will still be great at what they do.
—-
The same thing is happening in music. Everyone gets lifted but on different dimensions.
I’ve found ai tools most valuable for:
1. Quick “how to do x in y” language
2. Large scale refactorings that are mostly mechanical.
This still takes a bit of guidance to get the right output (and breaking down the refactoring an into multiple steps). But it does speed things up when I would touch 40-some files. I still review all the code.
Watch 2-3 onshape tutorial videos and then just dive in trying to make parts for yourself.
If you’re new to 3d printing you’ll soon learn that what you design doesn’t always print right. Welcome to creating things in the real world. This is part of the learning experience (and why you need to learn by doing).
Onshape also has a bunch of public cad designs, so you can look at how other people made things to learn (sort of like reading source code to learn).