bguthrie

6 ms·

1.
AI isn't a value-add for software; software is a value-add for AI(brianguthrie.com)
2 points by bguthrie 4mo ago|0 comments
2.
Software Architecture After AI(brianguthrie.com)
2 points by bguthrie 4mo ago|0 comments
3.
Show HN: Prospero Is Superpowers for Writing(brianguthrie.com)
4 points by bguthrie 4mo ago|1 comments
4.
Accumulated Ignorance at Scale(brianguthrie.com)
1 points by bguthrie 6mo ago|0 comments
5.
by bguthrie 7mo ago
His wife was a professor at the Northeastern computer science department when I went there. A wonderful teacher.
6.
Refuctoring [pdf](waterfall2006.com)
2 points by bguthrie 8mo ago|0 comments
7.
by bguthrie 10mo ago
I hadn't realized Zed was built from the ground up to support collaborative programming. I liked it already, and I like it even more now.
8.
by bguthrie 10mo ago
The problem with no collaboration is that it can lead to fragility . Context transfer is costly, but without it work bottlenecks around key individuals. When those individuals are explicitly disincentivized to transfer knowledge preemptive
9.
by bguthrie 1y ago
This was before Git! (Subversion had its meager charms.) Even after Git became widespread, some infra teams were uncomfortable installing a dev tool like Git on production systems, so a git pull was out of the question. The main issue that,
10.
by bguthrie 1y ago
I was working on Rails apps before AMIs or Heroku.
11.
by bguthrie 1y ago
My recollection is that this is what many Capistrano setups were doing under the covers. Capistrano was just an orchestration framework for executing commands across multiple machines. More than that, I worked for many enterprises that were
12.
by bguthrie 1y ago
I've been writing Rails code since 2007. There's a reason the stack has gotten more complicated with time, and virtually no team has ever done it right by this definition. The trouble with an omakase framework is not just that you
13.
The Move Faster Manifesto(brianguthrie.com)
1 points by bguthrie 1y ago|0 comments
14.
by bguthrie 3y ago
I spoke to the authors of this database while running my last startup about the exact problem this sets out to solve—the need for time-travel features in particular domains (versioning for everything!). Opens up a range of interesting optio
15.
The problem with reorgs is that you're not doing enough of them(orgspace.io)
2 points by bguthrie 3y ago|0 comments
16.
Why Orgspace Doesn't Use Algorithmic Challenges For Screening Candidates(orgspace.io)
1 points by bguthrie 3y ago|0 comments
17.
How Orgspace anonymizes data sent to ChatGPT(orgspace.io)
4 points by bguthrie 3y ago|0 comments
18.
by bguthrie 5y ago
I reviewed the article in question and have a little more color to add for some of the skeptics commenting below. Advocates of pre-merge review point out (correctly) that peer review is valuable: humans are fallible, and a second pair of ey
19.
by bguthrie 11y ago
I use Scala frequently for internal microservices development. I also write a fair amount of Clojure. I believe that a lot of good and robust software is built in Scala, but that it suffers from a kind of complexity fetishization that offse
20.
by bguthrie 11y ago
I think that talking about a 10x engineer or 0.5x engineer misses the right optimization: good software is built in teams, so build a strong team. Cross-skilling, pairing, and blocker removal all help give people a collective sense of commi
21.
by bguthrie 11y ago
Cursive is an excellent way to write Clojure and has improved my workflow tremendously. Highly recommended; I bought a license. Congratulations to Colin on a 1.0 release.
22.
by bguthrie 11y ago
I'm not clear what technique this article is trying to describe, but anyone that spends two weeks pre-writing tests is not performing TDD. That simply isn't how it works. The cycle is: red, green, refactor, repeat. That's per
23.
by bguthrie 12y ago
I remember working out of the same office as these guys back when they were just getting started, and their success and impact has been truly amazing. Recognition well deserved.
24.
by bguthrie 12y ago
Exception handling is currently my biggest complaint with core.async, and I've gained a fair amount of sympathy for the idea of encapsulating asynchronous operations inside an object that can accommodate failure states, like a future (
25.
by bguthrie 12y ago
Many demonstrably innocent people are indicted and convicted with far less evidence than a video. Nonetheless, for other cases I grant the point.
26.
by bguthrie 12y ago
The law doesn't do an especially good job of it either. Perhaps it would be better were we all more observant of the principle than we tend to be; the accused is not always guilty. Edit: For context, this is what I had in mind: https:
27.
by bguthrie 12y ago
Note that while the main header describes the topic as "the practice and craft of functional programming," the body text makes it clear that it is "a new conference for typed functional programmers." Thus the notable o
28.
by bguthrie 12y ago
Puzzles are a terrifically poor way of judging whether a candidate will be good at performing the most common form of programming there is: solving meaningful problems, often business or interface ones, in a simple and readable way. Your pr
29.
by bguthrie 12y ago
As a candidate, I'd much rather they ask; I find that companies that don't ask for code are almost by definition unlikely to ask the right questions. If you must screen candidates for skillset, the less you have to rely on a proxy
30.
by bguthrie 12y ago
I think the focus on immediate, actionable feedback is great, but I get really nervous when I see screenshots with graphs. Does peer to peer feedback happen often enough to merit such an analytical approach? Getting continuous feedback is a

More ›