I was hacking scripts and web shit together in perl, python and php for many years before learning C, and just a couple months learning C/C++ made me understand so many more basic concepts than all previous years experiences combined.
Address are written for humans.
For machines, the address line and postal code is the only important part, the rest is encoded in the postal code and can be left off.
Nah, our generation had to tinker with shit to get it working. Kids these days have it easy, which is good from a user perspective, but fails to train them how any of it actually works at a deeper level.
No one has to install a device driver anymore.
It’s a beginners book filled with a mix of bad and good advice, which takes considerable experience to separate the two. Those who can point out all the bad advice already don’t need the book, and newer developers will pick up absolutely atrocious coding advice. There’s simply better books that target beginners better, like The Pragmatic Programmer.
So when you are on-boarding junior devs that have bought into the clean code/SOLID dogma, you’re spending several months beating all their terrible coding habits out of them.
Programming is mostly research. Researching curses to cast on the guy who wrote the Incomprehensible mess you’re currently debugging.
apt remove sudo
sudo is not installed on several distributions by default, so hardly surprising it’s not there or that you can remove it.
Well yeah, 100% of programming errors are programmers fault.
Meanwhile PHP quietly runs 80% of the internet by being used for WordPress.
“There are only two kinds of languages: the ones people complain about and the ones nobody uses.”
Always remember, the silicon valley ethos of “break things” wasn’t about their applications, it was about breaking industry, society, laws and your ability to oversee or regulate them.
the tests are now larger than the thing itself
Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.
The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.
I’ve programmed C# for nearly 15 years, and have used goto twice . Once to simplify an early break from a nested loop, essentially a nested continue. The second was to refactor a giant switch statement in a parser, essentially removing convoluted while loops, and just did a goto the start.
It’s one of those things that almost should never be used, but the times it’s been needed, it removed a lot of silliness.
async/await was introduced in version 4.5, released 2012. More than a few releases at this point!
Like a fungus you learn to live with
considering how huge FB still is.
FB is only huge because they’ve expanded all over the globe, even providing internet to developing nations to facilitate new user acquisition. In reality they’ve been bleeding the original Western users that signed up between '04-'10, and growth among new generations flatland a long time ago. There’s a reason Meta aggressively expanded to other ventures (or attempt to create platforms) like Instagram, Threads, what’s app, VR and metaverse. Metas only chance at sustainable growth and capturing young people is to build or buy platforms young people will use, because it ain’t Facebook.
Apparently every code base I’ve ever worked on was run through this.
Remember when people were calling this dummy the “real life Tony Stark”? Lol.
SPAs are mostly garbage, and the internet has been irreparably damaged by lazy devs chasing trends just to building simple sites with overly complicated fe frameworks.
90% of the internet actually should just be rendered server side with a bit of js for interactivity. JQuery was fine at the time, Javascript is better now and Alpinejs is actually awesome. Nowadays, REST w/HTMX and HATEOAS is the most productive, painless and enjoyable web development can get. Minimal dependencies, tiny file sizes, fast and simple.
Unless your web site needs to work offline (it probably doesn’t), or it has to manage client state for dozen/hundreds of data points (e.g. Google Maps), you don’t need a SPA. If your site only needs to track minimal state, just use a good SSR web framework (Rails, asp.net, Django, whatever).
I took a compiler course focused on optimization and porting. So I worked with x86 and ARM. There’s very little reason in modern computing to write assembly by hand, but it’s still useful to be able to read and understand.