I'm guessing this has a lot to do with the tech stack. Unnecessary microservices and/or unnecessary front-end heavy tech like React. These kind of things make the stack taller, requiring more dev labor for the same surface area.https://twitter.com/rjs/status/1261443696538480640?s=20 …
-
Show this thread
-
Replying to @rjs
Also, I feel, an undervaluing of design and the iterations required in good work.
1 reply 0 retweets 2 likes -
Replying to @DanielZarick @rjs
We use React and have a similar ratio and don’t generally suffer in productivity from the tech as far as I can tell. Tools matter for sure but there is some measure of taste involved and a huge dollup of culture and practice.
1 reply 0 retweets 4 likes -
Yeah I think it’s more about “this team is more likely to overcomplicate what could be simpler solutions.” There are definitely good react codebases and very horrible rails codebases.
1 reply 0 retweets 2 likes -
Replying to @DanielZarick @rjs
respect for design, process, and iteration is the fundamental recipe Can be accomplished with a variety of stacks and tools.
1 reply 0 retweets 2 likes -
Replying to @jhooks @DanielZarick
Unnecessary complexity in tech is a tax. You can afford to pay the tax if you compensate in other ways. But you're still paying it.
2 replies 0 retweets 3 likes -
Ryan Singer Retweeted Ryan Singer
Re: "culture and practice" agree and would love to unpack that. This is one specific lead. Any others?https://twitter.com/rjs/status/1261467207470469120?s=20 …
Ryan Singer added,
Ryan Singer @rjsYes, at Basecamp we have the awesome advantage of designers who code. But it's not a two-level thing: from throwing hi-fi mockups over a wall → coding designers. There's a level between: throw the right 20% of the design over the wall to specify macro behavior. Huge gains.Show this thread4 replies 0 retweets 1 like
DZ Retweeted Ryan Singer
Your thread here gets at it best, I think. My own personal feedback loop as someone who designs + codes entire chunks of our app delivers allows ideas to be tested and dumped very quickly. You can’t scale that easily/at all with a large design/dev ratio. https://twitter.com/rjs/status/1261461913386405889?s=21 …https://twitter.com/rjs/status/1261461913386405889 …
DZ added,
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.