A good programmer can get more done than 10 bad programmers, but a bad programmer's code can keep 10 good programmers busy for years.
~ Ed Weissman

A decade ago 800x600 was pretty much the standard resolution for devices and 5 sec response time was considered fast. Animations were minimal and websites were easier to read. Programmers debated around topics like which loop runs faster, i++ or ++i, while vs doWhile and so on. In general, we were closer to understanding what happens behind the browser curtain and how code needs to be organized to make it more maintainable.

Today the level of abstraction is much higher. I don't think devs can contemplate on the finer aspects of programming efficiency; they'd rather rely on a code library to do all the grunt work. With the explosion of devices and platforms, the focus has shifted from programming to assembling. Programmers need to know their tools first, then write code. The tool is expected to work well with a millisecond response time, not the programmer's code.

Moving forward, I think programming would be more about building higher abstraction utilities/libraries that are integrated by other tools, which is already happening. Marketing an App would become more important than the actual skill needed to develop it.

A bit far-fetched, but I think the future programmer would be a lot like a stock market analyst who has a bunch of windows in front, just observing data or algorithm patterns created by an AI engine and cherry-picking a specific combination of modules that might make the next big sensational app.

<rant>
I fucking HATE the Arduino environment right now.

First of all: you can't fucking put your project files in a sub folder to the main file. I can't write #include "src/motor.hpp" because it doesn't fucking know what that means.
Turns out you have to put all your header files in the fucking library folder common for all Arduino projects!

Secondly, you can't call your cpp headers hpp, they HAVE to be called h, or the Arduino environment throws a fit and begins whining about being unable to find the fucking files.
Not just that! You can't reference other Arduino libraries from within your library because the environment doesn't know what that means either.
To get around that you need to fucking include the library in your main file, AND THEN you can include it in the library file that uses it. After all, it should be the programmer's job to soon feed a so called IDE, right?

I'M SO FUCKING DONE WITH THIS SHIT! 😤

I'm ready to either program the Arduino directly with an AVR programmer or even port the entire project to the raspberry pi where I have a proper fucking Linux environment with a proper fucking directory structure so I can code proper fucking C++.
Hell I'm even fucking willing to spend all weekend porting all the code myself if necessary.

It's not reasonable that correct fucking C++ code is invalidated because I called the files something "wrong" and put them in the "wrong" directory.
</rant>

"user friendly project board" my ass

Have a nice weekend programmer's!!!!!

I hope your code behaves on Monday the same way it did on Friday.....🤣😂🤣

Best Programmer's Breakup:
* me * used to code in Javascript and PHP
* Girl * Also a Programmer

Me: You are a semicolon to my code.
Girl: Awwwwwww.. That's so sweet.
Me: * Trying to breakup * I recently switched to Python and want to use only a single language now.

* It Works! *

P.S.: Still use all three Languages ❤

When having to fix parts from an other programmer's code, do NOT concentrate on the small code expected to be wrong, instead read and understand the whole program around it!

Best practice:
1) Why is this code here
2) What does this code do
3) How does the code solve the problem

(just happened to me 😅)

Found this in my programmer's code. Can I claim temporary insanity when they find his corpse?

I've not coded for quite some time but when people ask me to tell a story about my depression I write a code.

do u think that the aesthetics of your text editor affect the programmer's ability to code?

Whenever I reach the point where static analysis can't help me any further I always feel a sort of thrill mixed with terror. This is the real deal. Until now the problems were easy to find, the questions had well defined answers to choose from, the rules were universal. In the part of the logic that cannot be checked, the invariants upheld manually, where the best the type system can enforce is for the programmer to clearly state what they're doing, lies the real beast. In proofs commented on functions or invariants as logical expressions over plain English variables written in the doc comments of a struct.

In the blurry and pompous future I imagine for software development, that's where the programmer's time will be spent. Once we all agree on what a string is, what it means to depend on someone else's code, and what parts a UI should be made of, all a developer should have to do is make decisions and derive proofs an automated deduction engine can't do on its own.

!rant

I've been having this idea for a programmer's horror movie. The main villain is this dev (or maybe PM?) whose first program was "Goodbye World" instead of "Hello World", thus cursing all of his code from that moment on.

They write an artificial intelligence library but they don't document it properly so the user ends up creating an evil AI that threatens to destroy the internet.

Any ideas?

That's how programmer's do YOGA
Code In... Bug Out...