I find that it’s good to ask questions that allow them to vent further.

The trick is to do the hobbies for their own sake instead of using them as a means to an end.

The silver lining here is that the world has gained an extremely compelling argument for regulations.

Epics don’t have to be huge. And stories don’t need to be attached to epics in the first place.

An epic is just a way to organize features. There’s no hard and fast rule for how many features are needed to form an epic.

If the work is expected to make it into the deliverable product, then it should fall under a feature. Either add it to an existing feature or create a new one. I prefer the former because it results in less deceptive forecasts.

Methylphenidate always works. It’s just a question of dosage lol

You can report the malicious reddit cares message and get the reporting user banned.

I don’t know how things are today but when I was a kid, some of my textbooks and many of my worksheets were in comic sans.

Shit I might just try this out. I hope my colleagues don’t notice.

Shipping is essentially fan fiction. It’s fine as long as nobody takes anything too seriously.

Don’t take too long trying to figure out a challenge by yourself. Ask questions. Unlike in school, you are allowed to ask for help with your work.

Learn how to write unit testable code as soon as possible (SOLID principles). Learn how to write concise and relevant unit tests. If it’s not in your team’s culture to write unit tests, then you go be that guy. It’s good for you and it’s good for the product. Unit tests are one of the few things in the programming community that everybody believes are a good thing.

I became a full stack developer without realizing it. I don’t want more shit to do. God damnit let me hone the skills I already have!

I honestly just winged it. I came from C++ so you’re in a much better position to learn .NET than I was. There’s little need to get into the syntax. You can pretty much just wing it. It’s just OOP after all. You could probably look for some crash courses so that you can speedrun the language differences but other than that, you’ll do just fine using the official documentation.

Microsoft has free resources for their frameworks.

https://dotnet.microsoft.com/en-us/learn

The main reason to get into .NET is if you’ve started working for an employer that uses the Microsoft ecosystem.

Form a starting team based on skill sets and let them do the rest. Give them a project and they will tell you what they need if they feel assured that you have the capability and will to help them. You want the team to cater to the product, not to the manager because manager satisfaction does not bring value to the organization or the customer. You only need to manage more closely if for some reason you were only able to gather junior devs.