12 ms·

> The core of my argument is that we need to empower developers to discover what will lead to efficiency As others have answered, the answer is very obvious an

> The core of my argument is that we need to empower developers to discover what will lead to efficiency As others have answered, the answer is very obvious and doesn't need a lot of theorizing. Give good money and respect. Treat people as individuals (especially your mid/senior people). Accept that people will work on your team NOT because they believe in your product (they may in fact hate it) but because they need the money or the experience. This is not bad or wrong as long as they're being professional about it. Most important one is to not generalize, and to recognize nonsense that might creep into your thinking process. Most engineers have a great eye for spotting nonsense and they smell bullshit a mile away. > as the only way to lessen the load on the team is remove complexity of the application, and the only way to do that is to communicate between all of the domains Shaky assumptions upon shaky assumptions. These kinds of statements usually come from either a very experienced person or an extremely inexperienced one. From the substance of these statements it's obvious it's the latter and not the former. > The best way to communicate is to have someone who knows all of the domains. Honestly if you had started with this statement I wouldn't have replied at all because I would be 100% sure you're trolling. I can't even tell anymore. But this is way beyond unfounded.

ItsMonkk 5y ago
> These kinds of statements usually come from either a very experienced person or an extremely inexperienced one. Why not both? I'm an experienced developer with no management experience. This is exactly why I opened with "moving into". I do not believe that these are shaky assumptions, but have been proven by my development work. I am a man of many hats. Some of those hats are chiseled perfectly, some of them are rough. The way that I work out how to go about learning things is go down a utopian path and create myself a minimal example. Many times the approach falls apart right away. When they don't, like this one has, and the world isn't already working that way, I expect that I am wrong but don't know why. So I reach out on places like Message Boards and peers in an attempt to work out why. Unfortunately this thread has been filled with a lot of harsh responses that mostly show that I have blown peoples weirdness budgets and am outside of the Overton Window with no real substance. That may be partly my fault and I hope that I at least learned something from it.

ItsMonkk 5y ago

> These kinds of statements usually come from either a very experienced person or an extremely inexperienced one. Why not both? I'm an experienced developer with no management experience. This is exactly why I opened with "moving into". I do not believe that these are shaky assumptions, but have been proven by my development work. I am a man of many hats. Some of those hats are chiseled perfectly, some of them are rough. The way that I work out how to go about learning things is go down a utopian path and create myself a minimal example. Many times the approach falls apart right away. When they don't, like this one has, and the world isn't already working that way, I expect that I am wrong but don't know why. So I reach out on places like Message Boards and peers in an attempt to work out why. Unfortunately this thread has been filled with a lot of harsh responses that mostly show that I have blown peoples weirdness budgets and am outside of the Overton Window with no real substance. That may be partly my fault and I hope that I at least learned something from it.