I think I would prefer one rust developer over a fuck ton C programmers 😅

You would hope this was dead already... Given that you can version control even without server nowadays there's no excuse for a developer not to version control their code...

Templates in c++, when you think you know them they will stab you in the back. Love it :P

@allanx2000 complexity and solution scalability on a system level is far more complex than choosing between a list or hashtable, but being proficient in the basics helps a lot.

@Memeamphetamine no, most of those loops don't add anything complexity wise...

This code is not properly localized. Sweden celebrates the 24th...

'Fuck developers'? No, no copulation, just compilation

Hehe, moment passed, 1026 :)

Wow 1024 to be exact

C++ is a nice language. You can do anything and everything in it. But beware, there are so many ways to shoot yourself, and so many opinions on how to do things. It's very important to find nice simple patterns that work for your application and stick to it...

I feel there is too much of a long term cost in many of these technologies that are easy to get started in. Not that traditional tech shouldn't learn from the strong points, just that lack of typing for instance might be refreshing in the beginning but might become a real problem in a large project. Go feels like the best overall backend solution right now. Very traditional in many ways, with some refreshing ideas making it fun to work with.

No one would question a doctor reading up on new treatments between patients, right?

Relax and read up on new stuff. Try exciting new tech. If anyone questions that, just explain you have nothing to do and self education is an important part of the profession. It's an investment for coming projects.

https://dave.cheney.net/2012/01/...

I am not a fan of C in general, but there is beauty in the simplicity of the error handling. Errors are part of the contract or signature of a function, and I strongly feel that exceptions do little except hide that fact. I don't like the custom enums commonly used for errors I C however. The go model where you commonly return result and/or error (supporting multiple return calues) is pretty clean though.

The problem is that when used, exceptions are rarely exceptional. Normal errors are better communicated through normal program flow imo. The other problem is that it's so easy to ignore catching exceptions. I feel the c-style or even go-style way of doing it is better in the long run. I can accept exceptions for out of memory or similar really exceptional situations...

Avoid else, try to make function so that it exits in error checking if. Exceptions are not worth it... I have yet to see a convincing case for exceptions.

I could have written this ;(

No, but thank God my colleagues understand the complexity difference, and inner working of hashtables, trees and other useful data structures. Knowledge is power...

Wow this was literally me today. Find that I need to force myself to relax and reflect to not become slightly retarded under pressure.

I used to work with that application :) Many years ago now though...

Wow... Swing? They still include that in the jdk? :)

You need to find a way to separate yourself from your code. Take criticism as an opportunity to learn. It's not always easy, but it's important.

Numbered a few lines myself on my dad's old 286 in gwbasic :)

Same for me... QBasic was a great enabler at the time!

UML? I thought that died in the early 2000nds along with the misconception that a data exchange format for exactly all situations was a good idea.

Once, writing VM provisioning scripts, I was down 3 levels of escaping. That seriously fucks with your head!

Why? One of the best things with git is history rewriting. Think before you push (and that's mostly true when pushing to non-user branches)

Classic, leaks through the logging system is an often overlooked problem.

Oh, and find a way to deal with stressful situations that doesn't get to you. Projects come and go, but you're supposed to last a long time.