Matt Smith retweeted
Many engineering leaders feel they should be measuring *something*, but it doesn't make sense to measure *anything* unless you know *why* you are measuring. This is the question to start with, "What do you care most about?"
Matt Smith retweeted
Here's an exercise to discover the quality of your design as revealed by tests:
1. Print a test
2. Explain the scenario being tested aloud
3. While you explain, highlight the part of the test you mention
4. Look at the density of highlights
Matt Smith retweeted
Add "blocks" to your calendar so you can actually do some software development, since you are a developer 🥇.
Matt Smith retweeted
oh wow is-website-vulnerable 1.14.0 🎉
🔥 You can now specify a GitHub Action lirantal/is-website-vulnerable@master in your CI to test for vulnerable JavaScript frontend libraries. Big thanks to @mattorb 👏
Pull Request for how to use it: github.com/lirantal/is-websi…
Matt Smith retweeted
In discussions in engineering teams, you quickly see who has ever worked in a company that ran out of money and who has not.
Matt Smith retweeted
How I used a Github action to regularly trigger the Go-based broken link checker 'Muffet', to hold the line against 404 broken links on my web site.
{ author: @mattorb } #DEVCommunity
dev.to/mattorb/goodbye-broke…
Matt Smith retweeted
The way you address the problem is by shipping changes not more slowly, but more QUICKLY. Fewer, smaller changesets turn into debuggable, understandable deploys.
The delta from "writes code" to "code in prod" is the primary metric of a team's maturity and efficiency.
Matt Smith retweeted
2019 Accelerate State of DevOps Report is here!!! 🎉 Performance, productivity, and how to scale DevOps in the enterprise. Check it out! cloud.google.com/devops/stat… #ASODR #DevOps
Matt Smith retweeted
Things not working occasionally is more annoying than things that don't work at all
Matt Smith retweeted
You become a senior engineer once you've accumulated a sufficient number of "looking back, what was I thinking?" experiences.
Matt Smith retweeted
“Why did we decide to do it this way?” — every developer 12 months after making a decision.
big big mood from @iamagiantnerd at #LeadDevNewYork
Matt Smith retweeted
People work in systems. To understand their work, motivation, decisions, etc. you must also understand their system.
(Apparently today is RT @jpaulreed day. He is on 🔥)
Matt Smith retweeted
DevOps is a philosophy that extends Agile thinking to operations (and incorporates operations into development). These are not, and never were, separate things.
Matt Smith retweeted
❌ vendor talking at high level about product/service/OSS they created and want to sell.
✅ vendor giving deep tech talk on underlying technology. Teach me something I can't learn on glossy website.
✅✅✅ end user talk. Tell me about real world problems and (vendor?) solutions.
Matt Smith retweeted
A lot of programmers make the mistake of thinking the way you make code flexible is by predicting as many future uses as possible, but this paradoxically leads to *less* flexible code.
The only way to achieve flexibility is to make things as simple and easy to change as you can.
























