lanecwagner

Great insight, thanks for sharing. I believe your example is a good one. I'm still a believer that someone in your position should have a solid understanding of the architecture of your system, and likely experience with at least a part of it. That doesn't mean you need to be an expert in every domain, obviously, as that would be impossible.

I'm certainly blurring the lines a bit, but I would argue that in most cases there isn't a need for both. The tech lead can be the "manager".

"Managing people" isn't a full time job in most cases. It all depends on how the organization is structured and how many non-technical tasks are being assigned to the "manager". Sometimes a manager is responsible for product, marketing, or HR tasks and all that will be dependent on the company in question.

No, but IMO they should be one of the more technically competent people. Managing is not a full-time job, at least for a good manager its not a full time job.

Author here: this is something I wonder often. In companies I've worked at that had non-technical leadership in the engineering department I'm suspicious that they just played Bloons TD 4 all day. They certainly never seemed to have anything to do other than hire, fire, and go to meetings to have things explained to them.

A side-quel to my last post: https://qvault.io/2020/05/18/leave-scrum-to-rugby-i-like-get...

I'm actively building a solution for programming related content, with the goal being that courses feel like games:

https://qvault.io

While developing https://classroom.qvault.io I've been learning that I forget how not obvious literally everything about coding is.

In the first course I had feedback like, "I didn't understand code starts at the top and goes down"

Also a good call. I'm an engineer and suck at landing pages so it may take a minute to make it look nice ;)

Thanks for all the feedback! I just launched it today, I'll take this into account and offer some free functionality in the app

Author here, love the comments. The biggest criticism that makes me want to revisit and edit the article is the 2-month -> 4-month API example. I remain convinced that the Scrum process that I describe is OFTEN responsible for slowing down projects AT LEAST this much. That said, I think I need to come up with a better example. It's honestly hard to explain in words.

Mine is https://qvault.io/blog I guess I'm quite biased though :P

SWYgeW91IGZpbmQgbW9yZSBiYXNlNjQgYWZ0ZXIgZGVjb2RpbmcgYmFzZTY0LCBpdHMgcHJvYmFibHkgYSBrZXkgdG8gc29tZXRoaW5n

We plan on doing a mobile version down the line, but we have a lot of features for desktop to add first

The physical cards is our plan for monetization for now. If the community wants other options then we will probably pursue those!