|
Tuesday 20th February’s issue is presented by Sonar |
 |
Sonar: The Essential DevOps Automation Tool
Sonar analyzes your codebase quickly and accurately, giving you vital information to proactively fix any problems.
Correct issues from the moment code is written in the developer’s Integrated Development Environment (IDE) with SonarLint and utilize SonarQube or SonarCloud in the Continuous Integration (CI) pipeline to prevent issues from reaching production. |
|
|
The Management Team — Joel Spolsky
tl;dr: “Stop thinking of the management team at the top of the organization. Start thinking of the software developers, the designers, the product managers, and the front line sales people as the top of the organization... The “management team” isn’t the “decision making” team. It’s a support function. You may want to call them administration instead of management, which will keep them from getting too big for their britches.” Managers are administrators who aren’t supposed to make hard decisions but enable others to do so.
Leadership Management |
 |
|
Empty Questions — Ed Batista, Jennifer Ouyang Altman
tl;dr: “All too often our questions aren't truly open and honest inquiries. They may be loaded questions, freighted with biased assumptions. They may be leading... or simply be statements in disguise. The problem with these questions is that they're never as clever or well-hidden as we think they are. They feel hokey and theatrical.” Jennifer prompts us to ask empty questions, which release preconceived notions of what the answer is, not forcing an agenda or trying too hard. Empty questions come from a place of empowering, expanding and elevating. Examples are provided.
Leadership Management |
|
|
Modern DevOps Transformation Begins With Static Code Analysis
tl;dr: Many organizations implementing DevOps are facing significant underperformance issues. Learn how integrating Sonar static code analysis solutions can address these transformative issues, propelling organizations towards more efficient and secure software development and improving the efficiency of the current DevOps processes.
Promoted by Sonar DevOps |
|
|
Great Management And Leadership Books For The Technical Track — Nicole Tietz-Sokolskaya
tl;dr: “Over the years I've come across a few books that I really strongly recommend to everyone, but in particular, to people who want to advance on the technical track. Here are my favorites, along with why I like them!”
Books |
|
|
|
“Teams move at the speed of trust. Be the kind of dependable person you would want to work with.”
– Joel Goldberg |
|
|
The Ideal PR Is 50 Lines Long — Greg Foster
tl;dr: “50 lines is a sweet spot across speed, review comments, revert rate, and total coding volume. If you’re willing to accept a range, I can recommend 25-100 lines per PR. According to the data, we see that time-to-review, time-to-merge, and review comments per line all get better the smaller you make your PRs. There is a limit though: under 25 lines, and you start suffering a higher revert rate, as well as a lower total code shipped.”
BestPractices |
|
|
Google Zanzibar For The Rest Of Us
tl;dr: Google Zanzibar powers authorization for hundreds of Google’s apps so you might think it's a great model for your authorization service. But does Zanzibar's promises of scale, high availability, strong consistency mean that it’s the right solution for the rest of us? Zanzibar's defining characteristic is actually centralization, which is a massive tradeoff that’s not practical for most. The Googles of the world can pull it off, but is there a Zanzibar for the rest of us?
Promoted by Oso Infrastructure |
|
|
Ledger: Stripe’s System For Tracking And Validating Money Movement — Ilya Ganelin
tl;dr: “Ledger models internal data-producing systems with common patterns, and it relies on proactive alerting to surface issues and proposed solutions. Each day, Ledger sees five billion events and 99.99% of our dollar volume is fully ingested and verified within four days. Of that activity, 99.999% is monitored, categorized, and triaged through rich investigative tooling — while the remaining long-tail is reliably handled through manual analysis.” This post shares technical details on how Stripe built this money movement tracking system, and how teams interact with the data quality metrics that underlie our global payments network.
Architecture Scale |
|
|
Popular Git Config Options — Julia Evans
tl;dr: “I always wish that command line tools came with data about how popular their various options are, like: (1) “basically nobody uses this one”. (2) “80% of people use this, probably take a look”. (3) “this one has 6 possible values but people only really use these 2 in practice.” Julia asked about people’s favourite git config options and shares the responses.
Git |
|
|
Maybe Everything Is A Coroutine — Adam Nelson
tl;dr: Adam was inspired to develop a language in which all functions are coroutines, which has several cool features: (1) A type system in which coroutines are basically state machines. (2) A typed (algebraic) effect system based on coroutines. (3) A powerful exception system based on simple sum types. And more.
LanguageDesign |
|
|
|
Act: Run GitHub Actions locally.
Continue: Code with any LLM.
Fuzzy Search: Frontend library for searching objects.
Magika: Detect file content types with deep learning.
UV: Python package installer and resolver.
|
|
Click the below and shoot me an email!
1 = Didn't enjoy it all // 5 = Really enjoyed it
1 … 2 … 3 … 4 … 5 |
|
|
|