Just sitting in a train (Germany) while reading your rant. Meanwhile on the speakers: "we're arriving our next stop, we're 5 minutes early".. 😅 but agree, not a common situation

It might also just be an indicator to not invest too much. Not sure how long such a task usually would take, but adding some unneeded bells and whistles can add some time too.

Happened to me as well

I personally like qtcreator with vim plugin a lot for C++ development.

I'm Remembering my time studying (CS). Back then we had 2 girls out of around 100 students. Few years later our University introduced a more creative CS study (focussing on any kind of media) where around 50 % were girls / boys. I had the chance to get in touch with some classes and I couldn't see any difference from a performance point of view.
Looking at the market, I agree, most applications still come from guys (in our not so creative field), but the few applications we got from women were really promising and we hired most of them.
Additionally to the field of interest I think it still relates to social environments and given opportunities.
EDIT: I don't know how many girls are studying the CS thing I did today. So maybe it doesn't relate too much to the content itself

Also used to do it and had quite a good time with Slackware and other early distros. Ended up using Manjaro with i3 wm. Must admit I don't want to use any floating wm anymore. Tiling wm makes my life so easy.

@MrMarco mine has a physical mute button which turned out to be non functioning in only a few applications.

@TeachMeCode yes, think the early return is better suitable for checking the return value of a function on highest level. Then it's easy to follow the functions flow. And doing so you probably avoid nests more easily in the first place. But still, always depends.

I barely remember, but I think there is a MISRA rule that enforces to always have an else. Guess it is meant to tell the programmer that there is "always" a case where the if-statement fails and that needs to be handled or at least ignored explicitly.
I generally like the idea of early return, but that gets a bit hectic on nested statements in my opinion.

Another vote for Manjaro

Interesting thought. If I were to assess it, I'd wonder whether this isn't just a good thing in terms of having a socially compatible and thus effective team. But this probably depends on the type of team members

Take it easy. Working on complex things just takes time and making mistakes is just part of it. learn out of each single mistake .

You should make sure to get others outside of your current room "rm -rf /"

@Xoka think this is just normal for native and compiled executables. If not already done, try to use "make" or similar and make sure you use all cores for building.

I was actually surprised how easy and well it works. What's the reason you feel like that?

Cmake is not too bad if used properly.
But Ja, it still can get crazy

Classic Procrastination

Does it mean the majority of us is using c#, typecode, xcode, ..?

@AleCx04 just had glance right after my post and must say it feels pretty uncomfortable to me. But I truly believe it's worth to dig into, for several reasons. Right now I'm more into the raw stuff of Cpp , so learning a interpreted language is like learning a parallel universe I guess.but again, I think it'll be worth to do so. If you got any good resources I'll be happy to get them known 🙂

I'm the wrong guy here, but I can't remember ever to be able to introduce a feature in a week.
Is it only me?

I do not know anything about smalltalk and stuff, just curious how it compares to other languages with regards to performance and frameworks(basic libraries). 80 MB environment is quite small. But sounds interesting and think I'll give it a try

Say no and increase your reputation by doing no more intern jobs. The more you do, the more it gives a wrong impression (IMO). Interns are usually cheap, so if you can, don't sell yourself like this 🙂

I learned vim and enjoy the keybindings. There are so many tools and plugins out there which use them. Not sure if this is the same for emacs though. Vim keybindings you can setup in (but of course is not limited to) shells (zsh,..), webbrowsers (various plugins for major browsers, bunch of dedicated browsers like qutebrowser),IDEs(cannot remember an IDE that didn't have a plugin), window managers (i3,...), mail clients, file managers (ranger,..)

Of course some of them have just a limited subset, but it feels very straight forward if you can use the basics in most applications

I like the takeaway from that story. Also got the impression that reading isn't the first thing that's done (guess it comes after searching on SO)

@magicMirror I'm more thinking of standing in front of a whiteboard and trying to make up a design with the team (let's say in a Sprint planning 2 meeting or something similar). But get your point and agree. We tried to maintain UML as part of our documentation in former companies where we failed to do so. BTW I would count flowcharts to the set of UML diagrams (activity diagram)

@Voxera can't we use reflog on whatever branch got force pushed?
Some online systems like bitbucket even visualize it. Do I miss something?

@Lucky-Loek thanks for your opinion

I agree, it doesn't need to be perfect UML but it helps to visualize ideas

@magicMirror thanks for your opinion

must say I cannot totally agree. Saying UML isn't something you can use in agile makes me wonder whether we have the same understanding. As soon as you have to use other components, interfaces and sequences play an important role. It's not about documenting and keeping it up to date necessarily, it's more about getting a common understanding 🙂
In my opinion that's one of the fundamental misunderstandings of the agile manifest. It's not necessarily about documentation but having a language for individuals and their interaction.

@halfflat totally agree 👍
And this answer shows clearly what you're talking about. Thanks!
Template meta programming and related topics are equally important to me, though they are pretty language dependent (correct me if I'm wrong).
But Ja, having someone applying who understands both feels to be super rare (personal experience only).

@halfflat thanks for your opinion.
That's somehow what I expected to read.
IMO even in a small team its crucial for collaboration. Think most teams do not really experience it though, guess everyone has its own domain and only a few interfaces.
Just can tell how our team improved by reducing boundaries and working closely.
Additionally, knowing about UML and design patterns helps to solve already solved problems in a proven way. (just had good times extending some functionality by simply plugging in a new command into command pattern).

Maybe it's also different in other domains?