blakehaswell

5 ms·

1.
by blakehaswell 1y ago
One thing that might not be obvious about checklists is how they're used. I used to think checklists were used by reading the item, then doing the thing. I literally thought of them as a recipe that you would follow. Complete a step, c
2.
by blakehaswell 4y ago
I feel for everyone working there who is suffering whiplash from being pulled from one direction to the other. What can you possibly learn about a new feature in a few hours apart from the gut reaction of a mob? If that's enough to cha
3.
by blakehaswell 4y ago
Yes, WIP (work on progress) limits are a key feature of Kanban.
4.
by blakehaswell 4y ago
Citation needed. Whether the server is serving HTML or JSON it still needs to serialise the data, so I don't think serialising JSON is going to be significantly faster than serialising HTML. Plus then the client needs to deserialise th
5.
Virtual Memory Tricks(ourmachinery.com)
1 points by blakehaswell 4y ago|0 comments
6.
by blakehaswell 4y ago
To clarify, are you saying up to two-dozen services for a development team with ~12 developers on it?
7.
by blakehaswell 5y ago
I really enjoyed this, I think looking the organisational structure through time is a good take that I haven't really seen addressed so clearly before. I would have liked to see an exploration of the "through time" lens on so
8.
by blakehaswell 5y ago
> did Facebook, Apple, Amazon, Netflix, Google, etc all make a terrible engineering mistake? Is that so impossible? There are many other considerations that go into technology choices at these companies. There are trade-offs involved, an
9.
by blakehaswell 5y ago
What exactly do you mean by multiple entry points? Do you have multiple processes which run independently but are co-located in the same repository or are you talking about something else?
10.
by blakehaswell 5y ago
> great speed in iterating new features […] makes our customers happy For me this is a leap. I can't think of many examples of software which I use where new features have actually made me happy. Normally it's just change which
11.
by blakehaswell 5y ago
Back in 2014 Spotify released some videos[1][2] about their engineering culture. From what I understand these were widely cited by consultants and the squad/tribe/chapter model was implemented verbatim at a number of companies. I&
12.
by blakehaswell 5y ago
Not the person who asked, but I'm interested in the first two.
13.
by blakehaswell 5y ago
> Exactly what I did. After reaching top still somewhat technical position at the company I got so fed up and burned out that I quit. Went on my own and been this way ever since for some 20+ years. I'd love to hear more about your j
14.
Simple Code, High Performance – Casey Muratori [video](youtube.com)
3 points by blakehaswell 5y ago|1 comments
15.
by blakehaswell 5y ago
At the end of the day our software is going to run on real machines, sending data across real networks. I feel like we'll always be leaving performance on the table if we don't understand the characteristics of the hardware we&#x2
16.
by blakehaswell 5y ago
C++ provides programmer control over memory layout, which is something managed languages don't provide. So although C++ is an older language and it isn't designed for modern machines, it does allow you the control to make performa
17.
by blakehaswell 6y ago
Me too. I was trying to browse HN on my phone earlier and my first instinct was that my WiFi was having a moment. It's a testament to how reliable HN is.
18.
by blakehaswell 6y ago
Given their previous post about technology choices[0], I'd say modern C++ is probably ticking most of those boxes for the author. [0]: http://rachelbythebay.com/w/2020/09/24/feedback/
19.
by blakehaswell 6y ago
I was thinking "modern C++" is potentially a good fit for avoiding most of these complaints (i.e. if you solely use smart pointers). Given their other post about technology choices[0] I'd guess it's a safe assumption. Th
20.
by blakehaswell 6y ago
> If you actually don't need it (i. e., your hot methods are never overridden), then the JIT will trivially compile those "virtual" method calls as non-virtual ones. But isn't that the thrust of this article? Of cours
21.
by blakehaswell 6y ago
I agree. I don’t think lines of code is necessarily the right thing to budget, especially if you limit it to “lines of code written by our team”. But there is something interesting in this idea. Our software is growing immeasurably complex.
22.
by blakehaswell 6y ago
My concern with this is that it gives the "rain skeptics" a platform to spread their views, and presents "rain skeptics" as a legitimate alternative to the "rain scientists". The problem with this is that once
23.
by blakehaswell 6y ago
I'm not sure that's such a huge problem. HTTP routing provides a wonderful architectural seam so that we can use different solutions for different domains like `/profile` and `/document-editor`. We can create rich client
24.
by blakehaswell 6y ago
> to write off GraphQL or React as "cancerous" on account of someone having made a less than optimal decision in how to use them seems premature. Apologies, cancerous isn't how I'd describe it, but the sentiment of th
25.
by blakehaswell 6y ago
> From a purist perspective, this has a "cancerous" feel (as opposed to being "encapsulated") I have the same feeling about much of the React ecosystem (edit: though I'd say "tightly coupled" rather tha
26.
by blakehaswell 7y ago
> How much longer will this rumor persist that "good code" doesn't need commenting? Indeed. I recently came across an article[0] which does a good job of debunking this idea, and describing different types of comments and
27.
by blakehaswell 8y ago
For an accessible talk about the real-world implications of this, I enjoy watching Mike Acton's CppCon talk "Data-Oriented Design and C++": https://www.youtube.com/watch?v=rX0ItVEVjHc
28.
Data-oriented design and C++ – Mike Acton(youtube.com)
6 points by blakehaswell 8y ago|0 comments
29.
by blakehaswell 11y ago
I’ve been playing with microcontrollers for the last few weeks, where debugging typically involves reading data sheets more often than Googling, and I could definitely see myself integrating this type of workflow into my day job.
30.
by blakehaswell 11y ago
it's a lot of risk What’s a lot of risk? Saving a significant portion of your income? Sounds less risky than “work until I’m 70 and then hope I have a good pension.”

More ›