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 -
Not sure what you’re looking for, but I’ve worked with tons of devs (I myself am a designer who codes full stack) who just seem to have blindness towards simple solutions. I’ve never been able to unpack it or find a reason.
1 reply 0 retweets 2 likes -
Replying to @DanielZarick @jhooks
Agree that's probably irreducible in some cases. One has to combine lots of skills to find simple solutions. But I think the context is a big factor too. Devs are often given too tight constraints or no constraints. Shaping can unlock creativity by setting clearer boundaries.
1 reply 0 retweets 3 likes
Totally agree. I was a very young PM then and our whole culture was focused on tightly defining tasks+deliverables. I would always argue that by doing so we’d remove any ability for a dev to care about the solution let alone use more of their creativity to find a better solution.
-
-
Replying to @DanielZarick @rjs
the developer/designer distinction often gives developers the impression that they aren’t designers I love that Shaping removes the visual/graphic design aspects from the design process. Makes design more accessible.
0 replies 0 retweets 5 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.