`Simple, Boring Tech Stack: shell scripts over k8s, keep code modular`. wut
The Tiny Teams Playbook
31–40 of 50 posts
Re: The Tiny Teams Playbook
#32Earlier 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…
[flagged]
Re: The Tiny Teams Playbook
#33Earlier 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…
[flagged]
And you are being myopic, so I will counter your trite response with my own link which explains why LLM's are very useful for what they are, but in no way what the hype proclaims them to be, and never reply to you again either.
Re: The Tiny Teams Playbook
#34Earlier 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…
>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 those.
Re: The Tiny Teams Playbook
#35The 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…
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 collaborate with AI? Are these people building robot bodies for Claude’s GPUs and making those robot bodies sit in office chairs across from them? Would that make them more productive?
Re: The Tiny Teams Playbook
#36> 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
#37This 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.
Re: The Tiny Teams Playbook
#38The 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 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…
Re: The Tiny Teams Playbook
#39Earlier 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…
Got any evidence of this or is just vibes based?
Re: The Tiny Teams Playbook
#40Earlier 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.
this is true, and irrelevant to my reasoning.