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.
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.
public string GetDayOfWeek(DateTime date) => "saturday";
I also calculated it, his result checks out.
There is no dropping out, and there’s no replacement. All political donations have been to the Biden campaign, it is illegal to transfer those funds to a new candidate. The only person who could run for president in his place is Kamala, since she is the other person on the ticket.
It’s extremely clear no one talking has any clue how any of this shit works.
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.
Like a fungus you learn to live with
Apparently every code base I’ve ever worked on was run through this.
I never saw that, that’s legitimately funny. I’d love to be in the room when that feature was designed, and the reaction of the developer it was handed too.
I don’t know if the game is the best example of busineses making top-down design decisions, since that game was an obvious scam from the start.
Machines aren’t people. Machines don’t learn. Machines copy data, manipulate and replicate it. That is copyright infringement. The laws for Machine duplication don’t apply to human learning.
Or federal funding.
Canada did it right, and just named the city without adding new.
London Ontario, Paris Ontario, Berlin Ontario (before it was renamed over a minor European dispute).
Unfortunately Nova Scotia was already called that before it joined.
Remember when people were calling this dummy the “real life Tony Stark”? Lol.
Oh wow, I’ve seen this guys shorts start popping up constantly. He seems like he understands the algorithm enough to explode
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.