If you're interviewing dev candidates and *you* have to prepare and research a bunch of CS stuff you forgot? They're probably bad questions
— Max Lynch (@maxlynch) February 24, 2016
My computer science professor in college had all of his TAs take the exams in half the allotted time.
— Valerie @ Brighton Ruby (@valeriecodes) April 11, 2018
If the didn't get 100% he changed the questions.
There's a lesson there for tech interviews.
"The only way to get senior engineers reliably is to grow them" #phillyete
— Matt Brophy (@brophdawg11) April 11, 2016
1. Hire awesome people.
— David Neal 🥓🥑 (@reverentgeek) June 14, 2018
2. Teach them your stack.
It boggles my mind when I hear of companies that dismiss amazing candidates because they don’t have an exact recipe of knowledge and experience.
Your team is an immutable data structure. Every time you modify it, you're actually making a whole new one.
— Sarah Mei (@sarahmei) October 21, 2016
Culture defined at #phillyete pic.twitter.com/Ej6kfLrsJX
— Martin Snyder (@MartinSnyder) April 11, 2016
Velocity is a lagging indicator of team health. Team joy is a leading indicator of quality and velocity. @DocOnDev #AgileMetrics #PhillyETE
— Audrey Troutt (@auditty) April 12, 2016
Happy Birthday to President Harry Truman who said: "It is amazing what you can accomplish if you do not care who gets the credit" Onward.
— Matthew Dowd (@matthewjdowd) May 8, 2017
"We simply ask that you be innovative without mistakes while working as a team to achieve individual performance goals." ~@DocOnDev
— Woody Zuill (@WoodyZuill) May 7, 2017
"‘‘As long as everyone got a chance to talk, the team did well’’https://t.co/QlCTf1nCiO
— Martin Snyder (@MartinSnyder) June 15, 2018
You can passively consume hundreds of articles and podcasts and learn far less than shipping one side project a year.
— Ben Orenstein (@r00k) August 30, 2017
— lizandmollie (@lizandmollie) February 14, 2021
From an internal discussion, apparently derived from Peter Drucker: "Leaders focus on doing the right thing, managers focus on doing things right" That is going to stick with me.
— John Carmack (@ID_AA_Carmack) November 3, 2020
“Don’t cling to a mistake just because you spent a lot of time making it.”
— Halima 🧞♀️ (@imdatfeminist) December 6, 2019
― Aubrey de Grey
One thing my father always told me about being a manager is that if you're seen as a "boss" then you've failed. If you're doing it right, you're a colleague with a different specialization.
— Rebecca Turner (@ReBeccaOrg) April 12, 2019
Just finished reading "The five dysfunctions of a team". Such an insightful read!
— Gurpreet (@_zenx_) August 3, 2018
"If you could get all the people in an organisation rowing in the same direction, you could dominate any industry, in any market, against any competition, at any time". #teams #management pic.twitter.com/XdeSvfnDJ3
If you have to tell people something is mandatory, it's because you haven't convinced them that it's valuable.
— Erik Dietrich (@daedtech) August 4, 2017
"Every job looks easy when you’re not the one doing it” is one of my favorite new quotes.
— Morgan Housel (@morganhousel) July 14, 2017
Got my two copies of 'The Mythical man-month', ready for any PM who wants to read it twice as fast. pic.twitter.com/ptbRGFecf8
— Joseph Cooney (@josephcooney) September 16, 2016
Org 1 has a 10:1 eng manager to engineer ratio. Adding 1 more eng would be “no problem, could add 2-3”.
— John Cutler (@johncutlefish) May 1, 2020
Org 2 has a 5:1 eng manager to engineer ratio. Adding 1 more engineer would “be overwhelming”.
Equally skilled. Similar domain/context.
First one or two guesses at why?
what to talk about in 1:1s
— 🔎Julia Evans🔍 (@b0rk) August 30, 2020
(permalink: https://t.co/BzuyBWgG1s) pic.twitter.com/nUzBRphu1b
...or it will happen. pic.twitter.com/kyh9c5aAV1
— John Cutler (@johncutlefish) February 12, 2021
This morning I saw @Dixie3Flatline's tweet about how you can dislike a tool without writing a mean blog post.
— Chelsea Troy (@HeyChelseaTroy) May 8, 2021
I remembered a conversation with @KentBeck about critique: art students explicitly learn to critique the work of others. Engineers...don't, and it shows.
What do?
/1
"Don't take criticism from someone you wouldn't take advice from."
— 🧁🍨 Mark Dalgleish (@markdalgleish) May 10, 2021
This one helps a lot.
I’ve interviewed and managed over 2,000 people.
— Michael Girdley (@girdley) November 26, 2021
Here are my 55 contrarian observations about humans.
A thread...
(1/x)
As a manager, the more tactical decisions you make, the less competent your employees will appear to you.
— Doc Norton (@DocOnDev) October 13, 2022
#leadership
It’s highly doubtful that you’re an agile organization if every team in your company is using the same process. “Self-organizing teams,” are essential to agility, and if you’re told what to do and how to do it, you’re hardly self organizing.
— Allen Holub (@allenholub) July 22, 2018
This feels like going faster
— John Cutler (@johncutlefish) August 15, 2018
Vs.
This actually makes us faster#lean #prodmgmt #quality #agile #devops pic.twitter.com/nq8yT0Txz8
"How do we scale up our software practices?" The same way you scale up anything. By relinquishing control.
— jasongorman (@jasongorman) July 7, 2017
The fastest way to raise your level of performance:
— James Clear (@JamesClear) October 6, 2019
Cut your number of commitments in half.
I've written this before, but it bears repeating as it's the single most common piece of software engineering leadership advice I end up giving: Don't have people working by themselves, if it's worth doing it's worth having more than one person on it.
— kellan (@kellan) May 16, 2021
I'm always inspired by @ejames_c.
— John Cutler (@johncutlefish) October 10, 2021
He is always learning/doing in public, and writing about learning/doing. And brings you along for the ride.https://t.co/OCsjZiQspf
From one of our CEOs - an explainer of why change management often goes sideways. pic.twitter.com/QgKBBCQVRU
— Mark Brooks (@markbrooks) September 23, 2022
"A complex system that works always evolves from a simple system that works. A complex system designed from scratch never works." Gall's law
— Rob Kalin (@rokali) October 9, 2010
this database has a Scar Schema. deep, ancient wounds that never healed properly
— Jimmy Bogard 🍻 (@jbogard) May 3, 2017
"We build our computer (systems) the way we build our cities: over time, without a plan, on top of ruins." - Ellen Ullman
— Programming Wisdom (@CodeWisdom) July 4, 2017
"The sooner you start to code, the longer the program will take." - Roy Carlson
— Programming Wisdom (@CodeWisdom) October 18, 2018
"computers will not live up to their potential until we start to think of them less like televisions and more like paintbrushes" @mres pic.twitter.com/jyn2h2TGw7
— Rachel Thomas (@math_rachel) August 25, 2017
The Conjoined Triangles of Senior-Level Development https://t.co/6rDNYfHyqN pic.twitter.com/EMqSADspK9
— Pam Selle (@pamasaur) July 16, 2016
The problem with software development: pic.twitter.com/DzvPkB91e1
— John Ferguson Smart (@wakaleo) April 19, 2017
√ @viktorklang's Conjecture:
— brendan mcadams (@rit) October 12, 2016
“If you cannot solve a problem without programming, you cannot solve a problem with programming."
"The time saved by automation is the least value - it also documents how a thing is done" @jessitron #PhillyETE
— Tim "Agile Otter" Ottinger (@tottinge) April 18, 2017
"The type String should only ever appear in your program when a value is being shown to a human being"
— Mario Fusco 🇪🇺 (@mariofusco) June 10, 2017
- @nuttycom
"Any code of your own that you haven't looked at for six or more months might as well have been written by someone else." - Eagleson's law
— Programming Wisdom (@CodeWisdom) June 23, 2018
"A common fallacy is to assume authors of incomprehensible code will be able to express themselves clearly in comments." - @KevlinHenney
— Rich Rogers (@RichRogersIoT) April 19, 2017
If you don't think managing state is tricky, consider the fact that 80% of all problems in all complex systems are fixed by rebooting.
— stuarthalloway (@stuarthalloway) June 1, 2019
— Javi Velasco (@javivelasco) July 31, 2018
There are only three optimizations: Do less. Do it less often. Do it faster.
— M. J. Fromberger (@creachadair) September 11, 2018
The largest gains come from 1, but we spend all our time on 3.
“We need to know when this will done!”
— John Cutler (@johncutlefish) December 18, 2020
Me: what are you willing to exchange for that certainty?
I was keynoting at @droidconbos but also got rejected by an Android conf happening in the same month. Often you only hear the acceptances. pic.twitter.com/UXzat1xsJJ
— Chiu-Ki Chan (@chiuki) April 20, 2017
Thank you @jwwweber and all the speakers and organizers for a great #EmberCamp!! pic.twitter.com/o0bKsKIcf8
— Godfrey Chan (@chancancode) September 21, 2018
Okay. For every retweet this gets (TO A POINT!) I'll add a thought / tip / observation about speaking at conferences.
— Corey Quinn (@QuinnyPig) January 10, 2020
How to park. Geometry. https://t.co/EziMwgS83B pic.twitter.com/a5sHZUswnI
— Cliff Pickover (@pickover) November 26, 2016
After the invention of the bicycle, the average distance between birthplaces of spouses in England increased from one mile to 30 miles.
— Quite Interesting (@qikipedia) February 14, 2017
honestly robotic cranes stacking and unstacking useless concrete weights for all eternity is the surreal dieselpunk energy storage solution earth deserves https://t.co/4F4fDyWVg0
— crust lovers, this entree was made for you (@vogon) August 20, 2018
How the tracks of all known hurricanes show that they have never crossed the equator due to the Coriolis force https://t.co/D5r5vAC21c pic.twitter.com/l0mjjQ34cT
— Massimo (@Rainmaker1973) August 27, 2019
This is def my fave Hacker News post: "Name one idea that changed your life".
— Trung Phan 🇨🇦 (@TrungTPhan) October 3, 2021
Here are 11 gold answers 🧵
Imagine a system where a man gives you a chuck-e-cheese token every hour you let your car idle. Realize that system exists and it's bitcoin
— Krinkle (@Krinkle8) February 28, 2014
by today's definition, y=mx+b is an artificial intelligence bot that can tell you where a line is going
— Amy Hoy 🌵 (@amyhoy) March 29, 2017
The S in the IoT stands for Security.
— Oleg Šelajev (@shelajev) November 10, 2016
How to play: before leaving any office, write a load of absurd bollocks on the whiteboard for the next lot to puzzle at. #SillyWhiteboards pic.twitter.com/iEaytmfZla
— Jason Hazeley (@JasonHazeley) March 15, 2017
We did an experiment: For two weeks we switched names. I signed all client emails as Nicole. She signed as me.
— your friend, Marty Schneider (@SchneidRemarks) March 9, 2017
Folks. It fucking sucked.
Reminder of how much some dudes in this industry hate women.
— Lin Clark (@linclark) December 10, 2017
This comment is on my Quantum article, the 20th most upvoted post on Hacker News of all time pic.twitter.com/nCa5WB10Id
There’s a debate on whether 10x software engineers exist.
— Gergely Orosz (@GergelyOrosz) October 9, 2021
They do: I’ve seen several of them.
And their existence freaks the hell out of me. 5 examples of 10x engineers and why you should be afraid when you see one:
In response to narrowly spread demand, here are my Rules of Twitter. Note that each was learned by violating it repeatedly over the years, so don't bother going back in my feed to find contradictions... trust me, I know. pic.twitter.com/QtzhBkx9LP
— Peter Sagal (@petersagal) October 25, 2021
Totally agree. Sure, hard work, prepare, etc, but LUCK. Luck 100% played a part in my success.
— Scott Hanselman (@shanselman) February 27, 2019
Here's the thing though. Now that I have some success, *I'm* gonna *BE THE LUCK* for as many people as I can. That means RT's, warm intros, job referrals, hey you should talk to, etc. https://t.co/udw0mzfFpi