jrott

9 ms·

31.
Three Architectures for a Responsive IDE(rust-analyzer.github.io)
1 points by jrott 3y ago|0 comments
32.
by jrott 3y ago
This article is such a mix of hilarious and deeply frustrating. It does identify a real problem of people who get things done but what they have done is useless at best or harmful at worst. The issue is what to do about it. I’m guessing it’
33.
by jrott 3y ago
Probably deal flow. Seems like a good way to find AI startups.
34.
How to Work Well on Teams(abseil.io)
2 points by jrott 3y ago|0 comments
35.
by jrott 3y ago
"Languages and their tooling ecosystems express how computing is concretely embedded and used by society. People adopt the tools to get jobs and to get the job done, whatever the "job" is. In turn the available remunerative j
36.
El Paquete Semanal(en.wikipedia.org)
183 points by jrott 3y ago|51 comments
37.
The Beautiful, Brutal World of Bonsai(newyorker.com)
3 points by jrott 4y ago|1 comments
38.
An Oral History of Hugops(protocol.com)
2 points by jrott 5y ago|0 comments
39.
by jrott 5y ago
Also works for health data as well[0] if anonymity is actually important it's really hard to collect data at all. [0] https://www.nature.com/articles/s41467-019-10933-3
40.
Suez Canal blocked by traffic jam after container ship runs aground(cnn.com)
5 points by jrott 6y ago|0 comments
41.
Internal Tooling Is Underrated(jrott.com)
2 points by jrott 6y ago|1 comments
42.
We Need 4 Waves of Climate Action(globalecoguy.org)
3 points by jrott 6y ago|0 comments
43.
On “Technical Debt”(dondo.org)
1 points by jrott 6y ago|0 comments
44.
If the Fire Goes Out(esquire.com)
3 points by jrott 6y ago|0 comments
45.
Kingdom: The Mitanni, with Mara Horowitz(peoplingthepast.com)
2 points by jrott 6y ago|0 comments
46.
Goliath's reckoning: Has REI grown too large?(snewsnet.com)
1 points by jrott 6y ago|0 comments
47.
Collections: The Universal Warrior, Part III: The Cult of the Badass(acoup.blog)
6 points by jrott 6y ago|0 comments
48.
Yet Another List of DevOps Resources(jrott.com)
2 points by jrott 6y ago|0 comments
49.
by jrott 6y ago
not sure you're going far enough there. Obviously we need a scrum king to guide our scrum lords as they help our scrum masters transform our organization.
50.
by jrott 6y ago
> In my experience, code with too many functions is more difficult to grok than spaghetti code. It's like trying to read a book with each sentence reference a different page. So, I try to code like I would write, in digestible chunk
51.
by jrott 6y ago
There is a real trap in always feeling like you need more career wise or comparing how you are doing to other people. It's way too easy to shift the goal to being a little bit more successful then you currently are and it makes people
52.
America Is Running Out of Nurses(newyorker.com)
4 points by jrott 6y ago|0 comments
53.
by jrott 6y ago
I didn't see it either. Hoping it's semi-reasonable because I'd like to be able to really use it.
54.
by jrott 6y ago
Yeah developing actual customer facing features is the goal. That paragraph needs to be edited
55.
by jrott 6y ago
Author here I actually think spreadsheets are great because they are so accessible. What isn’t great though is when there is a business processs that is a spreadsheet and knowledge that exists in one persons head.
56.
Buy Don't Build(jrott.com)
232 points by jrott 6y ago|218 comments
57.
by jrott 6y ago
Actual debt has a few major differences with tech debt though. First it's easy to quantify the cost of. Second and more importantly where it's good and bad are almost the opposite of where tech debt is good and bad. You want to us
58.
by jrott 6y ago
Tech debt is a bad metaphor. Having lots of debt can be a smart business decision. The problem is usually engineers do a terrible job telling the story around why having lots of tech debt will cause problems. Usually if you've got non
59.
Iron, How Did They Make It, Addendum: Crucible Steel and Cast Iron(acoup.blog)
281 points by jrott 6y ago|25 comments
60.
by jrott 6y ago
Most of the worst production issues I've been involved with have come from trying to fix a minor issue and then somebody making a mistake. The way our brains are wired to handle stress isn't really useful for debugging complicated

More ›