The office or otherwise mandatory frequent in person work sessions bit seems pretty at odds with the underlying idea that you’re a team focused on actually delivering and building with deep focus. What does commuting a half hour, hour, or more, each way to an office to put my headphones on and zone in, do to achieve any of that? I’m gonna be able to do that more effectively, more focusedly, and at the hours I’m most…
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…
The Tiny Teams Playbook
41–50 of 50 posts
Re: The Tiny Teams Playbook
#42Earlier quoted context omitted.
Hacker News formula for startups: no offices, no offsites, no meetings, and no MBAs. If only idiot CEOs and rapacious VCs were listening!
Not quite. Have an onsite team or have hybrid setups that bring people within geographic areas together. Nothing replaces getting around a physical whiteboard in a physical space. Context is in the original statement that retreats are a fix for burnout.
Re: The Tiny Teams Playbook
#43Earlier quoted context omitted.
Not quite. Have an onsite team or have hybrid setups that bring people within geographic areas together. Nothing replaces getting around a physical whiteboard in a physical space. Context is in the original statement that retreats are a fix for burnout.
I used to agree with that but now we have tools like Figma that actually work better than a whiteboard once you understand how to use them correctly.
The concept being that you break things down and layer in details so the evolution is explained similar to the train of thought from live sessions.
I've been remote almost exclusively since 2012 and have used everything out there... the biggest thing that makes an improvement with remote comms? A very high quality microphone with a high quality compressor / gate (hardware, even) and using Mumble / Teamspeak / etc with a good codec where everyone can hear everyone speaking at the same time with low latency. That's what we lost from copper phones and it's exponentially worse in Zoom where you can't tell when someone is trying to interrupt you with the auditory cues. It really makes a big difference.
I'm an extrovert so I love video / cams on but really audio is all that is needed when paired with a tool like Figjam and getting high quality audio makes a remarkable difference.
Re: The Tiny Teams Playbook
#44Earlier quoted context omitted.
Yep, 2-4x onsites together a year to develop human relationships, and otherwise 100% remote, is by far the most effective team arrangement IME. It is especially the most accessible format for people who do not necessarily perform their best work within the typical office hours (9-5, +/-1), who do not want to live in your metro area, or who are distracted by disturbances in their surroundings - or just aren’t hardcore…
Quarterly is a lot, depending on travel distance and whether weekends are needed for travel, for folks with families.
Re: The Tiny Teams Playbook
#45Earlier 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…
Agree, and the difference between the floor and ceiling is typically leadership. Not just by the executives but everyone who works there.
Re: The Tiny Teams Playbook
#46Earlier quoted context omitted.
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…
Quoting wikipedia: >Researchers generally hold that a system is required to do all of the following to be regarded as an AGI:[34] > - reason, use strategy, solve puzzles, and make judgments under uncertainty > - represent knowledge, including common sense knowledge > - plan > - learn > - communicate in natural language > - if necessary, integrate these skills in completion of any given goal Modern AI can do all of th…
Re: The Tiny Teams Playbook
#47Earlier quoted context omitted.
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…
Quoting wikipedia: >Researchers generally hold that a system is required to do all of the following to be regarded as an AGI:[34] > - reason, use strategy, solve puzzles, and make judgments under uncertainty > - represent knowledge, including common sense knowledge > - plan > - learn > - communicate in natural language > - if necessary, integrate these skills in completion of any given goal Modern AI can do all of th…
1 - reason, use strategy, solve puzzles, and make judgments under uncertainty
2 - represent knowledge, including common sense knowledge
3 - plan
4 - learn
5 - communicate in natural language
6 - if necessary, integrate these skills in completion of any given goal
Only 2 (partially) and 5 are applicable to LLM's, as they are statistical text (token) generator algorithms. Very useful ones, no doubt, but not ones which satisfy all of the above.Re: The Tiny Teams Playbook
#48Earlier quoted context omitted.
Quarterly is a lot, depending on travel distance and whether weekends are needed for travel, for folks with families.
Agree, 4x is doable only if you have no kids. Otherwise you not only create a lot of stress for the other parent but you also lose valuable time with your family, which you won’t recover as kids grow up. I feel like 2x is reasonable.
Re: The Tiny Teams Playbook
#49Earlier quoted context omitted.
> The office or otherwise mandatory frequent in person work sessions bit seems pretty at odds with the underlying idea that you’re a team focused on actually delivering and building with deep focus. It’s at odds with being pro-AI too. If you can’t effectively collaborate with somebody who is not physically present but is just a voice on a call or words on a screen, what does that imply about how effectively you can c…
But AIs aren't humans, so why would we need to interact with them the same way? AIs also don't fill the same role in a team as humans do (at least, not in the kind of team discussed in this post).
One could argue that some AIs are like SOME humans. After all, you and I are both humans but we are not the same and no reason why our colleagues would interact with us in the same way. Nuance
Re: The Tiny Teams Playbook
#50The office or otherwise mandatory frequent in person work sessions bit seems pretty at odds with the underlying idea that you’re a team focused on actually delivering and building with deep focus. What does commuting a half hour, hour, or more, each way to an office to put my headphones on and zone in, do to achieve any of that? I’m gonna be able to do that more effectively, more focusedly, and at the hours I’m most…
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 have heard people state this like it is obviously true. Not so sure.