ryanartecona + teams   88

Bazel Fawlty
A fairly scathing experience report and review of the Bazel build system.
compilers  teams 
march 2018 by ryanartecona
Kitchen Soap – On Being A Senior Engineer
About the importance and meaning of "maturity" as a software engineer.
programming  management  teams  communication 
september 2017 by ryanartecona
re:Work
A Google initiative to share practices and guides to help teams and orgs to function well and support individuals.
hiring  management  diversity  teams 
september 2017 by ryanartecona
Abstractivate: Hyperproductive development
TL;DR: the most productive development happens when one person knows the system intimately because they wrote it; this is in conflict with growing a system beyond what one person maintains.
teams  communication  management 
june 2017 by ryanartecona
You Are Not Google – Bradfield
An argument for making technology decisions based on evaluation and need rather than cargo culting from other companies and choosing the cutting edge.
teams  programming 
june 2017 by ryanartecona
18F: Digital service delivery | The Dark Standup
A team took 2 weeks to work exactly 8 hour days and observed how things changed or didn't for them.
teams 
february 2017 by ryanartecona
Tough and Competent — Russ Garrett
On the perils of sloppy engineering culture and not being realistic with timelines and quality, from the perspective of the failed Apollo 1 space mission.
teams  communication 
january 2017 by ryanartecona
Some things that might help you make better software | David R. MacIver
An excellent list of factors that make for an effective (or ineffective) engineering org, from the Hypothesis author. Analogous to "12-factor app", but for teams.
testing  teams  communication  programming 
october 2016 by ryanartecona
HN comments are underrated
An absolute treasure trove of the best Hacker News comments.
community  programming  communication  teams  business 
october 2016 by ryanartecona
Work at different management levels | Lara Hogan
A nice breakdown by engineering director at Etsy of the types of work she has done at different management levels.
teams  management 
october 2016 by ryanartecona
Programming Sucks
How the environment of programming on a team is hostile and stressful and maddening and terrible even though programmers don't do physical labor.
teams  tech 
july 2016 by ryanartecona
oop - Functional programming vs Object Oriented programming - Stack Overflow
A classic Norman Ramsey SO answer on when to choose FP vs. OOP.
fp  teams 
may 2016 by ryanartecona
When to Rewrite from Scratch - Autopsy of a Failed Software · Code Ahoy
What to evaluate before committing to a wholesale rewrite, through the lens of a failed rewrite done for the wrong reasons.
teams  communication 
april 2016 by ryanartecona
Joe Duffy - Performance Culture
Strategy and tactics for fostering an engineering team culture which values and delivers on performance, and why it's a necessary component of delivering on performance goals.
performance  teams  communication 
april 2016 by ryanartecona
We only hire the trendiest
How certain hiring biases can be economically very bad for a company, and some other practices and focuses which can get more value out of the same team.
teams  hiring 
march 2016 by ryanartecona
On asking job candidates to code
The various forms of coding-project interview one person has seen at companies they've worked for.
hiring  teams 
march 2016 by ryanartecona
Is group chat making you sweat? — Signal v. Noise — Medium
A post from 37Signals/Basecamp about the scenarios which group chat in a team is most appropriate for, and all the myriad ways it's abused in inappropriate scenarios.
teams  communication 
march 2016 by ryanartecona
How to Write a Git Commit Message
Very thorough git commit message guide.
teams  git 
february 2016 by ryanartecona
People can read their manager's mind
On stated versus actual values in a managing role.
teams 
january 2016 by ryanartecona
The economics of software correctness
"If you want better software, make or find tools that reduce the effort of finding bugs."
teams  programming 
october 2015 by ryanartecona
Teach, Don't Tell / Steve Losh
A complete, thoughtful, and example-driven guide to writing technical documentation.
programming  teams  education 
october 2015 by ryanartecona
Say What You Mean :: nklein software
A very short treatise on encalsulation and readability.
teams  programming 
september 2015 by ryanartecona
How we ended up with microservices.
Discussion from an engineer from SoundCloud who helped decide why and how they would move from a monolithic Rails app to microservices, and the other process changes motivated by the same goals.
programming  distributed-systems  ruby  teams 
september 2015 by ryanartecona
::..: glen.nu :.: ramblings :.: on code review :.::
Some great thoughts on how to be good at and support your team colleagues with code review practices.
community  programming  teams 
august 2015 by ryanartecona
Feature Toggles are one of the worst kinds of Technical Debt
Great article on the pitfalls of feature flags in a codebase if done sloppily, better alternatives than large gated features, and helpful suggestions on how to handle them as a team when they are warranted for the operational benefits.
programming  teams  ops 
august 2015 by ryanartecona
The role of a Senior Developer - Matt Briggs
A very level-headed breakdown of how to classify the seniority of a developer without relying on time spent in the field.
teams  programming 
july 2015 by ryanartecona
Why do some developers at strong companies like Google consider Agile development to be nonsense?
A great set of arguments arguments for why Agile or Scrum are not conducive to a good engineering workplace.
programming  teams 
april 2015 by ryanartecona
« earlier      
per page:    204080120160

Copy this bookmark:



description:


tags: