Play one (!) round of online Backgammon (or whatever board or card game you prefer) and get back to the topic afterwards. Can be especially helpful at the beginning of large projects, when there's not a good balance between effort and reward yet.

I was born in 1973, and the most classical games I remember are Space Invaders, Asteroids, Centipede, Pac-Man and Donkey Kong.

I use tabs bc using spaces is rude. For example, I personally prefer .html or .xaml files with an indentation of 3 spaces, for other file types I prefer 4 spaces. This is not possible if some ruthless predecessor inserted spaces according to his, probably different, personal preferences in the source files. Or if I am the predecessor, then I would force my 3 spaces upon other people. That's not the way to treat each other.

Hi! My name is... my name is... tsh-k, tsh-k, Slim Shady!!

I missed the latest stuff, as we are still using Visual Studio 2017. But in my opinion, null propagation, named arguments and lambdas are useful and increase readability. I haven't tried switch expression, but they look like the same goes for them. I'm not familiar with ?[] and (_, _, area)=...! Does it mean you can return multiple values? Looks a little untidy compared to returning an object.

As C# includes many features that you also have in C++ and C, you could use C# as a language for absolute beginners, as long as you start with a very small subset of everything that's possible in C#. No lambda expressions, no null propagation, no classes, no properties etc., just some loops and branches, and maybe some functions. And then you can slowly work your way up to the more advanced features.

I would like to. But there's no one there. Aside from me, everybody prefers to stay at home for work. Just once a week I have an appointment with one particular co-worker in the office, which is better than nothing. The coffee in the office is so much better! ;-)

I've been using good old WinDiff since 1997, and I still like it. Sometimes I also use Tools.DiffFiles in the Visual Studio Command Window.

It's the UX designers, not the programmers! ;-)

With "everybody" I meant every developer. The religious people are usually managers. ;-)

Asphalt 8: Airborne by Gameloft My favorite game ever! And the only one I'm currently playing.

Everybody hates SCRUM. I do, too. But I think, the larger the team and the more innovative the project, the more SCRUM you need. Unfortunately! Haven't seen anything better for teams of 5-8 or more people yet.

"Coding" nowadays has become mostly web or mobile. As web has been around longer than mobile, it looks more familiar to most non-tech people.

On my work computer, I prefer the unobtrusive plain white standard cursor. On my home computer, which is also connected with my tele on the other side of the room, I use red bc it's easier to spot when sitting far away from the screen.

I'm always ready to migrate. For any software installed on my machine (except for free stuff, which can be downloaded again), I archived the setups + serials in my personal folder, so I can install again on any new machine. And my personal folders (Documents, Desktop etc.) are not stored on the computer's drive but on an external USB drive. Although I must admit on a laptop it wouldn't be practical do always have an external USB drive connected. But in addition, I'm doing a differential backup of all relevant folders to a second external USB drive once a week using "FreeFileSync", so I could just take the backup and copy it over to a new laptop, if I ever bought one.

I agree with you, aside from your point that just talking to each other is enough in large teams. From a certain team size on (maybe ~8+ programmers), I don't see how it can work without agile. In an innovative environment, where the project goals change several times over time, it's almost impossible to keep everyone heading in the same direction without any formal procedures. I also find them painful, but I see the necessity.

Without having any professional experience, it's always more difficult to get a job. So you should expect to be invited to numerour interviews and then not be picked for the job because there's usually someone else with professional experience, who will be preferred by the employer. It's a question of luck and a matter of time. Once you have 2-3 years of experience, it will be easier applying for your next job. And then you can be more picky when it comes to "good" or "not-so-good" jobs. For your first job, just make sure they don't fleece you, financially.

Blazor | Build client web apps with C# | .NET[^] Advantage: no learning JavaScript required. JavaScript is the only reason why I haven't become a web developer. It's not a language, it's a disease. :mad:

General question - general answer: I mainly see different pros/cons than you: Duplication: It's really bad when the different copies of the same code start to drift apart. It has to be made sure that whenever someone changes one copy of the code, the changes are copied to all other copies of the code. So everyone in the team has to know that there is copy/paste code, which might be a problem in large teams or teams with a lot of fluctuation. If you're a one-man team, then you don't have this problem. Unless your memory is bad and you can't remember what you did last year! ;-) Complexity, or as I would call it, "clean code": It takes a lot more time to avoid copy/paste code, and the return on this investment is not visible on the surface. There are cases where it's more efficient to not make this investment. So the decision depends on whether you're working on a one-shot project or on a product you're going to have to maintain for decades. For long-term software, the clean-code approach usually pays off in the long term. The *very* long term! Which is something that project managers usually don't like to hear and thus software developers have to take care of themselves.

My dev system isn't backed up at all. I am responsible myself for storing all vital data either on a network drive or in Subversion. In my home office via slow internet connection, where should the backup data be stored anyway? If my computer should ever go up in smoke (which never happened in my 24 years as a software develper), I never lose more than 1 week of work. 24 years of regular backup would mean much more effort than 1 week of work, so it's not worth it. My opinion!