AWebOfBrown

5 ms·

1.
by AWebOfBrown 24d ago
I honestly think Yegge has reached a point where he knows he isn't interested in doing the leg work of today's software engineering, but wants his career to ride the wave. The lowest effort, maximum value to extract in his positio
2.
by AWebOfBrown 8mo ago
If you're interested in hosting it at no cost on Oracle Cloud's always free tier (4 cpu, 24GB ram), instead of buying a Mac Mini or paying for a VPS, I wrote up how-to with a Pulumi infra-as-code template here: https://
3.
Friend's Guide to Agentic Engineering(abrown.blog)
15 points by AWebOfBrown 8mo ago|0 comments
4.
by AWebOfBrown 10mo ago
https://www.medlink.com/news/from-blood-sugar-to-brain-relie...
5.
by AWebOfBrown 1y ago
It doesn't, but from my perspective the thinking behind zero trust is partly to stop treating networking as a layer of security. Which makes sense to me - the larger the network grows, the harder to know all its entry-points and the tr
6.
by AWebOfBrown 1y ago
Another interpretation of this is that the lead developer adequately mitigated the risk of errors while also managing the risk of not shipping fast enough. It's very easy to criticise when you're not the one answering for both, es
7.
by AWebOfBrown 2y ago
I really wanted to adopt tRPC but the deal breaker was it being opinionated on status codes without allowing configurability. Because I needed to meet an existing API spec, that meant ts-rest was a better option. I think there's an adi
8.
by AWebOfBrown 2y ago
I think that's demonstrably false. His point about the runtime complexity of an API being entirely distinct from how the interface to it's code is exposed (whether GraphQL or REST or otherwise) is fairly obvious, I think. The coun
9.
by AWebOfBrown 4y ago
Everything I needed to know about Russell's performance war was answered when, whilst he was working at Google, folk started asking him why he was naming and shaming companies for poor performance when his exact critiques were swiftly
10.
by AWebOfBrown 4y ago
> Folks seems to lack a kind of basic economic perspective. I agree with most of what you said, but this seems a bit ironic. Your suggestions almost exclusively involve large investments of time with little established proof that they ar
11.
by AWebOfBrown 4y ago
Agree that try/catch is verbose and not terribly ergonomic, but my solution has been to treat errors as values rather than exceptions, by default. It's much less painful to achieve this if you use a library with an implementation
12.
by AWebOfBrown 6y ago
The reality is that I've heard unit, integration and e2e almost entirely used interchangeably, maybe except the former and latter. I don't think trying to nail down the terms to something concrete is necessarily a useful exercis
13.
by AWebOfBrown 6y ago
I don't think it's poor to test http handling either, as a coarse grained integration test. The problem I've seen is over-dependence on writing unit tests with mocks instead of biting the bullet and properly testing all the b
14.
by AWebOfBrown 6y ago
In the latter example, the question is really one of how tightly you wish to couple the application layer to that of the infrastructure (controller). Should the application logic be coupled to a http REST API (and thus map application error
15.
by AWebOfBrown 6y ago
If you have an aggregate root, it is responsible for knowing when changes to the aggregate have occurred, and thus making those visible. What is the mechanism for it to do so? Does the aggregate root retain the events and decide when to dis
16.
by AWebOfBrown 6y ago
> Could you explain which aspects specifically require a lot of boilerplate code? Probably the most frustrating part for me is tackling domain events and the implementation of the aggregate root. How have you tackled broadcasting domain
17.
by AWebOfBrown 6y ago
This is interesting to me as someone who loves DDD but finds the tactical side hard to implement in Node. A few questions stand out: AFAICT implementing tactical DDD involves a lot of boilerplate code. That seems to be consistent with what
18.
by AWebOfBrown 6y ago
Fargate is considered a serverless service. Serverless generally encompasses FaaS + BaaS. Think anything whose infrastructure you can use without touching the underlying VM(s): SQS, SNS, EventBridge, RDS, Lambda, Fargate, Athena, Kinesis an
19.
by AWebOfBrown 6y ago
This doesn't sound like the worst way to reduce expensive reads of normalised data. Is the implication that it should have been solved with views, was incorrectly normalised, or that a document/key-value store should have been use
20.
by AWebOfBrown 7y ago
I thought Messenger was ReasonML's flagship use-case inside Facebook. If so, it will be interesting to know what impact this has on its development.
21.
by AWebOfBrown 7y ago
Any chance you'd be happy to elaborate on what your role is? Are you primarily part of a dev-ops team, or tackling Kubernetes as part of developing the product? Did you obtain CNCF certification / think there's much value in
22.
by AWebOfBrown 7y ago
Or, phrased differently, from working another job.
23.
by AWebOfBrown 7y ago
A quote about salary, that I bookmarked as I could see myself making the same mistake: "Salaries never stay secrets forever. Hiding them only delays the inevitable. Last year we were having a discussion at lunch. Coworker was building
24.
by AWebOfBrown 7y ago
Can you elaborate on what they are, for the curious?
25.
by AWebOfBrown 8y ago
Is it still the case that one realistically needs to write their layout in flexbox as a fallback? Last I checked grid support was about 87% globally. I learned grid at one point but then just ignored it on the basis that if I had to write e
26.
by AWebOfBrown 8y ago
> How can any server administrator trust Matt Holt or his software again? I sincerely hope much of the community views this kind of personal attack on an open source developer for what it is: disgusting . If this kind of behavior is enc
27.
by AWebOfBrown 8y ago
Because laws and the consequences for breaking some of them are often morally questionable to a large portion of society. Compounding that, the judiciaries' understanding of esoteric technical topics can be sub-par, and a juries'
28.
by AWebOfBrown 8y ago
I felt the __typename was really awkward too, but Peggy Rayzis (of the Apollo team) told me awhile ago that they're working on removing that requirement, if it hasn't been done already. I don't think it's anywhere near a
29.
by AWebOfBrown 8y ago
You might want to fish up the MobX users list in one of its github issues. The users list is huge, and includes rather large projects such as Battlefield 1's UI, CoinBase and I think the new MS Outlook to name just a few.
30.
by AWebOfBrown 8y ago
Performance was my main concern with MST, most notably if your data modelling involves A LOT of entities, things can get slow: https://github.com/mobxjs/mobx-state-tree/issues/440 . Binding methods on every in

More ›