Steve Bering retweeted
Features put leaves on branches. Architectural investment builds new and stronger branches.
Steve Bering retweeted
We can all agree or disagree about whether it’s a good challenge or misery to work with legacy code, but I can declare with authority that it’s indeed miserable to work with poor quality legacy code when you aren’t empowered to do anything to fix it.
Steve Bering retweeted
Make an architectural decision. But don’t get attached to it. Until the decision has been tested, expect it to be wrong - and be ok with that. With experience, batting average goes up, but it is the same process.
Steve Bering retweeted
[wrapping up a 2 hour meeting]
- ok, any other business?
[person in suit] yeah I just wanted to circle ba-
me:
Steve Bering retweeted
Are you a public speaker?
Worried whether your presentation is good enough?
Ask yourself this question: 'Is my core message worth remembering?'
Refine your presentation until the answer is 'yes'
Steve Bering retweeted
“Both times it hit me like a gut punch. I have the perfect idol, because that’s what my idol is: Perfect.”
I’m up on the #Discoblog this week, and this post has been rattling around in my heart for months. Read and exhale. ❤️ discochurch.com/2018/07/17/4…
Steve Bering retweeted
Pride makes it impossible to believe in God’s sovereignty.
-Kevin Yi
@discochurch #thisweekatchurch
Steve Bering retweeted
Aging is the continual process of realizing what an idiot you were a few years ago. – at Dallas, TX
Steve Bering retweeted
Sometimes you have to get in trouble--good trouble, necessary trouble--to make a way out of no way.
Steve Bering retweeted
A successful development team is like a bees nest. Give them trust and autonomy to do their work, and they'll happily make you honey. But if you continually mess with the nest or heavily dictate the process, you risk reducing production and angering the bees. 🐝
Steve Bering retweeted
Jeff Bezos on the difference between “Type 1” and “Type 2” decisions is so great sec.gov/Archives/edgar/data/…
Steve Bering retweeted
Use `$ git log --oneline --no-merges [last tag]..` to generate the rough beginnings of your CHANGELOG entry:
Steve Bering retweeted
“No time to do it right, always time to do it again” #EverySoftwareProject (quote by @UdiDahan )
Steve Bering retweeted
"Every great developer you know got there by solving problems they were unqualified to solve until they actually did it." - Patrick McKenzie
