asyncrosaurus

u/asyncrosaurus@programming.dev
1 posts · 97 comments

Recent posts

Recent comments

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.

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.

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.

Ivermectin is an anti-parasite drug used in treating heartworm. It was one of the early conspiracy cures for covid, despite the fact viruses are notoriously different from parasitic roundworm. There was also a constrained supply of the drug used for human treatments, so the qanon types were buying the version of the treatment meant or horses.

on The last hope · c/memes · 3 pts · 2y

public string GetDayOfWeek(DateTime date) => "saturday";

I also calculated it, his result checks out.

on please · c/memes · 2 pts · 2y

I've used various Linux distress on a half dozen laptops over rhe last 10 years and I've never had Wi-Fi driver issues

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.