Jonathan Buch retweeted
Backlogs and Sprints are the two worst things that we were gifted by Scrum. The backlog allows you to "plan" in advance - the idea being that you know what to build, and it's just a matter of building it. You get folks to estimate it, so you can have a sense of how long it takes
Jonathan Buch retweeted
As a software developer, you may be called upon to perform some of these tasks in your career.
How well a CS degree prepares you for these tasks (and whether it even should prepare you for these) is left as an exercise to the reader.
🧵
1/
Jonathan Buch retweeted
what problems do people solve with strace? jvns.ca/blog/2021/04/03/what…
Jonathan Buch retweeted
The big thing we do in Legacy modernization is breaking up monoliths. This leads to more moving parts, so it's more complex, while less coupled. ~ @bellmar at @dettechwatch
Jonathan Buch retweeted
How do you deal with “once you’ve owned something, you own it forever” eating up most of your Sr folks time, not having bandwidth to take on new work? Or just being tired of owning something you made years ago? How is ownership compatible with transition plans, I guess?
Jonathan Buch retweeted
...we have the *awesomest* users. 😍 check out this meaty dive into distributed tracing @SlackEng -- its use cases, constraints, implementation, peculiarities, and so much more.
splendidly written, astonishingly concise. a fun, brisk read! 🌈✨ slack.engineering/tracing-at…
Jonathan Buch retweeted
For the past month, I've experienced coordinated harassment via 4chan on one of my GitHub repos. Yes, the platform I work on. Doing much better after taking time off & getting support from my circle. 💜 I'm ready to share my experience, so here it is: tinykat.cafe/on-all-that-fuc…
Jonathan Buch retweeted
i say this all the time, but people who are looking for "observability for k8s" are missing. the. point.
the point is not the k8s.
the point is for the k8s to be boring-ass infra, just a few high cardinality tags.
the interesting stuff is in your application. always.
You’re unable to view this Post because this account owner limits who can view their Posts. Learn more
Jonathan Buch retweeted
Who owns the code? Who is accountable?
How about: nobody. The code owns us.
Then, developers practice a kind of servant-leadership.
Jonathan Buch retweeted
Your readers aren’t stupid, yet that “simple” thing isn’t.
buff.ly/2YyQSYF
Jonathan Buch retweeted
A startup begins with a fluid development process. As it grows and has more at risk, it must grow structure.
An enterprise is full of structure. In agile transformation, it tries to grow fluidity.
That's a lot harder!
Jonathan Buch retweeted
Great advice in this HN thread: What do top engineers you know do that others don't? news.ycombinator.com/item?id…
Jonathan Buch retweeted
The main point is that since facts are written to a log as primary storage (and not deleted) there are infinite numbers of ways of reinterpreting these facts.
Jonathan Buch retweeted
I've been working with a large-ish startup that's revamping their incident response and incident program, and ended up writing up notes on some of the phases and challenges of creating and operating these programs.
Some tips!
lethain.com/incident-respons…
Jonathan Buch retweeted
This article from the Amazon Builder's Library might be on the evolution of continuous deployment at AWS, including pre-production testing, config testing and testing in prod ...
... but the most important takeaways here are actually the cultural ones.
bit.ly/34A2yKr
Jonathan Buch retweeted
Fun Fact: If you're using go + db/sql + postgres you should `SetMaxIdleConns` and `SetConnMaxLifetime` to reuse connections, rather than constantly opening new ones. Pretty easy to see the change in @honeycombio h/t @poolski see also alexedwards.net/blog/configu…
