Twitter | Pretraživanje | |
Adam Tanner
I write software sometimes.
2.774
Tweetovi
258
Pratim
261
Osobe koje vas prate
Tweetovi
Adam Tanner proslijedio/la je tweet
DHH 2. velj
Unless you follow up your “it depends” or “it’s all about trade-offs” with an actual disposition of WHAT it depends on or HOW to weigh those trade-offs, you’re saying less than nothing. It’s an intellectual pause button.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Ana Betts 1. velj
Odgovor korisniku/ci @anaisbetts
When you put related code together, you get to *choose* the order that people read the code, and you can optimize it for understanding. One Class Per File is ceding this order to what is effectively randomness, instead of Thoughtfulness
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Matt Stratton can have a little devops as a snack 30. sij
I'm so happy to share the updated version of our Full Service Ownership guide from ! Extra special shout-outs to for all their contributions to this.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Jaana B. Dogan 🌳 (in London) 24. sij
All abstractions leak because things need to be debugged.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Gergely Orosz 22. sij
Software architecture gets challenging when multiple devs need to decide how to design a solution. This is why developers who are seen as great software architects are very strong at seemingly unrelated skills: negotiation, driving consensus and facilitating efficient meetings.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Jeff ♨️ Darcy 22. sij
Junior engineers are not yet proficient at writing code. Mid-level engineers are proficient at coding but not software engineering, so they just squirt out tons of code without a thought. Senior engineers know that software engineering means *thinking* about code.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner 16. sij
Odgovor korisniku/ci @GergelyOrosz
“Yeah, the tests are flaky sometimes, but it’s not a problem in production.”
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Ari Clark 9. sij
There should be a FailConf. The speakers would share stories about a time they failed then discuss what they learned and how they recovered from that failure.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Camille Fournier 12. sij
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Paul Osman 30. pro
Some thoughts on environments and running code in production:
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Howard Dierking 3. sij
Breaking apart a monolith into a distributed system is no more objectively good than a monolith is objectively bad. You have to have teams of distributed systems devs - not enterprise devs plus a couple architects who figured out how to stand up k8s.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Avishai Ish-Shalom 14. pro
When you tell me you are a "senior" engineer, I expect you: Read RFCs Write documents Present to your peers Know how to discuss in writing Understand tradeoffs Back arguments with data Know how to manage meetings Self manage Prove there's a problem before you implement a solution
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Tashas[E]v 11. pro
Never underestimate the motivating power of telling someone they're doing a good job
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Justin Searls 9. pro
What do you think is the most effective way for leadership at a company to get the honest and accurate opinions from people who work at the company?
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
emma schwartz 6. pro
Tech companies are built on the backs of their Customer Support teams They perform constant emotional labor to remedy errors that they didn’t make, so that PMs/eng/design/ops/sales doesn’t have to. They protect a company from its own mistakes & should be revered, not exploited.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner proslijedio/la je tweet
Matthew Garrett 6. pro
He's making a list He's checking it twice He's got no idea who's naughty or nice Data consistency in a distributed environment is extremely difficult
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner 7. pro
Odgovor korisniku/ci @goldibex @raggi @ReinH
“Self-Replicating” sounds like we could be doing something vaguely AI-related so we should be $50M minimum.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner 7. pro
Odgovor korisniku/ci @raggi @goldibex @ReinH
The initial white paper: “Macroservices: Having Your Cake and Eating It Too (The architecture that CAP theorists don’t want you to know about)”
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner 6. pro
Odgovor korisniku/ci @raggi @goldibex @ReinH
When we start to run out of money we’ll introduce macroservices, the next generation of single server scalability.
Reply Retweet Označi sa "sviđa mi se"
Adam Tanner 6. pro
Odgovor korisniku/ci @raggi @ReinH
All this says to me is that our startup will be super legit.
Reply Retweet Označi sa "sviđa mi se"