4 ms·

Without noticing you might have pointed out one of the reasons founder type people are founder type people. Blindly follow orders isnt really on most startup f

Without noticing you might have pointed out one of the reasons founder type people are founder type people. Blindly follow orders isnt really on most startup folks’ list of things to do.

WWLink 2y ago
> Blindly follow orders isnt really on most startup folks’ list of things to do. The really funny thing I'm thinking about here is when I bring people onto a project I'm leading: I give them an intro to the project, all of the components at play, the needs of the project... and then introduce them to something they could work on and the general gist of what needs to be done. For some people that's enough to take it and run (and check in with feedback, minimal viable product, look for "does this sound good?" kinda stuff). For others it really feels like they need to be spoonfed an entire spec down to block diagrams, flowcharts, sequence diagrams, etc. And I've worked with teams that wanted that before we even assigned any software engineers to the project. Meanwhile I'm trying to get SOMETHING on a computer so we can start looking for the bugs that take a long time to manifest themselves. (and "that's not what we were expecting it to do!" from the systems team lol) Anyway, I can say that's not necessarily a big enterprise vs startup thing. It's more of a team vs team thing. IDK about startups.
- thinkingkong 2y ago
  Oh! Yeah I think I know what you mean. I - personally - would attribute that to fear. People from certain experiences or backgrounds dont want to be wrong or look bad. So they’ll demand a spec instead of being given general guidance. To me people who need spoon feeding and entirely dismissable if they cant be coached. The whole style that seems to work best is “we need to cross this river” rather than “build me a temporary pontoon bridge that can carry a tank”.
  - peterhi 2y ago
    Oh god we had this in team building exercises in the woods. "Here's a pile of junk, work out how to cross a stream without getting wet". One guy grabbed a long piece of wood and vaulted over the stream, others weren't satisfied until they had incorporated every single item from the pile of junk into the solution It suddenly made it clear how each person worked that I couldn't see in the office
    - WWLink 2y ago
      lmao at the "One guy grabbed a long piece of wood and vaulted over the stream" that's efficient as hell lol.
tom_ 2y ago
I assumed OP is well aware that the question is why these people took the big tech job in the first place, because it is obvious that it would be like this. Is this rocket science? I say no.

Without noticing you might have pointed out one of the reasons founder type people are founder type people. Blindly follow orders isnt really on most startup folks’ list of things to do.

WWLink 2y ago

> Blindly follow orders isnt really on most startup folks’ list of things to do. The really funny thing I'm thinking about here is when I bring people onto a project I'm leading: I give them an intro to the project, all of the components at play, the needs of the project... and then introduce them to something they could work on and the general gist of what needs to be done. For some people that's enough to take it and run (and check in with feedback, minimal viable product, look for "does this sound good?" kinda stuff). For others it really feels like they need to be spoonfed an entire spec down to block diagrams, flowcharts, sequence diagrams, etc. And I've worked with teams that wanted that before we even assigned any software engineers to the project. Meanwhile I'm trying to get SOMETHING on a computer so we can start looking for the bugs that take a long time to manifest themselves. (and "that's not what we were expecting it to do!" from the systems team lol) Anyway, I can say that's not necessarily a big enterprise vs startup thing. It's more of a team vs team thing. IDK about startups.

thinkingkong 2y ago
Oh! Yeah I think I know what you mean. I - personally - would attribute that to fear. People from certain experiences or backgrounds dont want to be wrong or look bad. So they’ll demand a spec instead of being given general guidance. To me people who need spoon feeding and entirely dismissable if they cant be coached. The whole style that seems to work best is “we need to cross this river” rather than “build me a temporary pontoon bridge that can carry a tank”.
- peterhi 2y ago
  Oh god we had this in team building exercises in the woods. "Here's a pile of junk, work out how to cross a stream without getting wet". One guy grabbed a long piece of wood and vaulted over the stream, others weren't satisfied until they had incorporated every single item from the pile of junk into the solution It suddenly made it clear how each person worked that I couldn't see in the office
  - WWLink 2y ago
    lmao at the "One guy grabbed a long piece of wood and vaulted over the stream" that's efficient as hell lol.

tom_ 2y ago

I assumed OP is well aware that the question is why these people took the big tech job in the first place, because it is obvious that it would be like this. Is this rocket science? I say no.