Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Tiny Teams Playbook

latent.space

Post reply on HN
Print view View original

21–30 of 50 posts

Re: The Tiny Teams Playbook

#21

Post by snoman »

copperroof wrote: post #12
rhubarbtree wrote: post #9

Earlier quoted context omitted.

The commute doesn’t help you, but working in an office next to your team mates will accelerate your work. Software development is a team sport and individual productivity is not the same as team productivity. Communication bandwidth in person is much higher when colocated. Startups move fast and higher bandwidth increases velocity, reduces errors, improves quality and team cohesion. For other situations remote can be…

I use this kind of opinion as my idiot bat signal now. It’s so obviously untrue when someone starts spouting this nonsense you know they are a very feelings based decision maker.

I have been leaning the other way. There’s room for nuance in the discussion but a stance of certainty that full remote is just more effective screams “expert beginner.”

Re: The Tiny Teams Playbook

#22

Post by christophilus »

snoman wrote: post #21
copperroof wrote: post #12

Earlier quoted context omitted.

I use this kind of opinion as my idiot bat signal now. It’s so obviously untrue when someone starts spouting this nonsense you know they are a very feelings based decision maker.

I have been leaning the other way. There’s room for nuance in the discussion but a stance of certainty that full remote is just more effective screams “expert beginner.”

There’s a third option: some people work best alone / remote. Some people work best in an office.

Re: The Tiny Teams Playbook

#23

Post by sabareesh »

"Simple, Boring Tech Stack:" Good advice but bad example, because it depends on what engineers are familiar and comfortable with and technology itself should be mature enough. You dont want to spend time building orchestrator when k8s solves it for you. Most cloud provides provide you with k8s as a service, which are miles better than using shell scripts, if you are already familiar with k8s

Re: The Tiny Teams Playbook

#24

Post by Spooky23 »

klardotsh wrote: post #10
rhubarbtree wrote: post #9

Earlier quoted context omitted.

The commute doesn’t help you, but working in an office next to your team mates will accelerate your work. Software development is a team sport and individual productivity is not the same as team productivity. Communication bandwidth in person is much higher when colocated. Startups move fast and higher bandwidth increases velocity, reduces errors, improves quality and team cohesion. For other situations remote can be…

I’ve worked in plenty of startups (the overwhelming majority of my career, actually) and did not perceive the performance of in-office teams to be significantly better than the remote teams I’ve been on. The floor is probably lower for remote teams (in that ineffective remote teams are horribly ineffective), but the ceiling is comparable, and the average is (again, in my experience) anywhere from comparable to slight…

I think it depends on your job role. I’m more architecture and operations in past lives, and being together is really powerful and reduces time taken for many tasks.

If you’re an engineer or developer mostly working a backlog, totally different story - wherever you are most comfortable working is ideal.

Either way, dogma is terrible. I have a friend who is a specialist in a specific area of finance who has been WFH for 20 years. Now she’s commuting to an office in a city about 300 miles away from the rest of her team, because the big boss says come to the office.

Re: The Tiny Teams Playbook

#25

Post by bdcravens »

> Top of market salaries: 95th+ percentile salaries

Absolutely. Pay, in real money, today. (as opposed to promises of future riches if all goes well)

If you're trying to do more with less, you can't afford not to.

Re: The Tiny Teams Playbook

#26

Post by kiratp »

leetrout wrote: post #13

> Camaraderie, speed: Have fun, do retreats, avoid burnout Or, alternatively, respect personal boundaries and don't force coworkers to have social outings. I really wish "work is just work" was more popular. There is an empathetic way to do this that isn't just treating people as a number but also not forcing socializing outside of the context of work. Yes to avoiding burnout. No to thinking a retreat is the answer t…

The kind of people in these small teams are not ones to think "work is just work".

Re: The Tiny Teams Playbook

#27

Post by snoman »

christophilus wrote: post #22
snoman wrote: post #21

Earlier quoted context omitted.

I have been leaning the other way. There’s room for nuance in the discussion but a stance of certainty that full remote is just more effective screams “expert beginner.”

There’s a third option: some people work best alone / remote. Some people work best in an office.

There’s more than 3 options. That’s what the nuance is about.

Sometimes individual productivity isn’t even the measure of success and sometimes it needs to be sacrificed for group productivity.

Re: The Tiny Teams Playbook

#28

Post by [deleted] »

swyx wrote: post #18
abuani wrote: post #7

This was a very challenging article to read. Not because any of the concepts described, but for the way ideas are thrown around and organized. This looks like it was written by a set of llm agents that were instructed to write an article without a clear outlined, and then the author took what they felt were the best bits and hit publish.

(i'm the author) it was 100% human, i'm afraid to say. i was trying to summarize a lot of content in a concise article.

[deleted]

Re: The Tiny Teams Playbook

#29

Post by AdieuToLogic »

swyx wrote: post #18
abuani wrote: post #7

This was a very challenging article to read. Not because any of the concepts described, but for the way ideas are thrown around and organized. This looks like it was written by a set of llm agents that were instructed to write an article without a clear outlined, and then the author took what they felt were the best bits and hit publish.

(i'm the author) it was 100% human, i'm afraid to say. i was trying to summarize a lot of content in a concise article.

An erroneous summarization is:

  The Tiny Teams concept has resonated so strongly that it’s 
  pretty clear it is the next major transition of the org 
  chart as we go from level 2 to 3 AGI.
LLM's, nor any offerings based upon them, qualify as Artificial General Intelligence[0]. So to assert there is an existing "level 2" AGI, let alone a progression to "level 3" AGI, is nonsensical.

0 - https://en.wikipedia.org/wiki/Artificial_general_intelligenc...

Re: The Tiny Teams Playbook

#30

Post by swyx »

AdieuToLogic wrote: post #29
swyx wrote: post #18

Earlier quoted context omitted.

(i'm the author) it was 100% human, i'm afraid to say. i was trying to summarize a lot of content in a concise article.

An erroneous summarization is: The Tiny Teams concept has resonated so strongly that it’s pretty clear it is the next major transition of the org chart as we go from level 2 to 3 AGI. LLM's, nor any offerings based upon them, qualify as Artificial General Intelligence[0]. So to assert there is an existing "level 2" AGI, let alone a progression to "level 3" AGI, is nonsensical. 0 - https://en.wikipedia.org/wiki/Artifi…

[flagged]
Post reply on HN