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
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
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
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
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
"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.
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
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 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
"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
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.
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
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
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
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