kpmah

7 ms·

1.
AI Review Loops Don't Always Stabilise(kevinmahoney.co.uk)
3 points by kpmah 23d ago|0 comments
2.
by kpmah 6mo ago
Experimenting with operational transforms with https://rootdoc.app
3.
by kpmah 10mo ago
I wanted to try a non-trivial project with AI assistance and I enjoy writing compilers, so https://vegen.dev I'll write up my experience in a blog post
4.
by kpmah 2y ago
I watch this show, but one of the most annoying things about it is that the traitors are incentivised to murder the smartest, most intuitive players first, leaving people they can manipulate easily. Maybe you could argue the smartest move i
5.
GitLasso: A small tool for managing multiple Git repositories(github.com)
3 points by kpmah 2y ago|1 comments
6.
by kpmah 2y ago
I recently came across (but haven't yet used) Typia, which appears to let you do validation with regular TypeScript syntax: https://github.com/samchon/typia
7.
by kpmah 3y ago
Author here, 8 years on. Although the advantages are real, I can't say I have had much opportunity to implement schemas like this. The extra complexity is usually what gets in the way, and it can add difficulty to migrations. I think i
8.
by kpmah 4y ago
Another misconception is that they somehow scale horizontally "better". They do let you scale components independently of each other, but this isn't as useful as a lot of people seem to think it is.
9.
by kpmah 4y ago
Even if it doesn't directly cause extinction, it could do things like destabilise nuclear powers.
10.
by kpmah 5y ago
Science denial. It's not going to stop at 'a little warmer'. https://skepticalscience.com/10000-years-warmer.htm
11.
by kpmah 5y ago
A review of 'Apocalypse Never': https://yaleclimateconnections.org/2020/07/review-bad-scienc...
12.
by kpmah 5y ago
Obviously you're in a better position to evaluate the trade-offs for your application than I am, so I'm not saying your decision is wrong, but this can potentially decrease availability if your application depends on both PostgreS
13.
by kpmah 5y ago
To spell out good reasons for doing this: If you're already using Postgres, you can avoid increasing operational complexity by introducing another database. Less operational complexity means better availability. You can atomically modi
14.
by kpmah 5y ago
I'm a type enthusiast, but dynamic languages make a lot of sense for small programs that either give you an immediate answer or fail to run (i.e. not long running, few branches). In those cases, the difference between a compile-time ch
15.
by kpmah 5y ago
I've worked at a place where this was cargo-culted and it worked horribly. All the worst aspects of 'services-first' design. I think this works much better when each team is working on what could be regarded as a complete end
16.
by kpmah 5y ago
The NHS is one of the most efficient health systems in the world.
17.
by kpmah 5y ago
The discussion here is frustrating because people are assuming that you'd pass the SQL directly to your database backend and expose your entire schema and all your data. SQL is just a query language, just like GraphQL, and is no less &
18.
by kpmah 6y ago
This spreadsheet-style functional programming is quite similar to a (very limited) prototype I wrote a while ago: https://kevinmahoney.co.uk/ocell/#example/polynomial.json
19.
by kpmah 6y ago
To add to that, I think the biggest thing to take away from Conway's law is that splitting teams of developers becomes a technical problem. If your goal is to efficiently build a product, technical expertise needs to go into that decis
20.
by kpmah 6y ago
I think what I'm trying to say is that my definition of a module as a "unit of encapsulation or understanding" is the more inclusive and general one, as it includes network and process boundaries. The OP's use of the wor
21.
by kpmah 6y ago
Specifically in the context of modules, I think it is a bad thing. It's hard to describe because I do it quite intuitively, but (very broadly) the way I find module boundaries is by trying to find the minimal interface for the maximal
22.
by kpmah 6y ago
IMO this is a confused take on modularity. I think isolation and security are related concepts, but not what modules are for. Those things have to follow module boundaries, but they're not the goal of modules. For me, modules are about
23.
by kpmah 6y ago
The main problem I have with the 'monolith first' advice is that it implies 'microservices later'. It feels like people have forgotten how to build good, simple, modular code.
24.
by kpmah 6y ago
If it is so obvious, why are all the legal challenges, even the ones involving Trump-appointed judges, failing? Why can't the challengers come up with a scrap of evidence?
25.
by kpmah 6y ago
As with Rust's 'unsafe', the fact that you can explicitly circumvent checks doesn't make those checks useless. If something goes wrong you know exactly where to look.
26.
by kpmah 6y ago
But, in the general case, who is this lowest common denominator programmer you are writing for? I can probably work out a few lines of terse Haskell more quickly than a page or two of boilerplate Java, because that's what I'm fami
27.
by kpmah 6y ago
> have a DefaultContract entity of some kind somewhere This is the OO mindset described at the bottom - the odd compulsion to have a reified entity for every concept. A lot of people have missed that the representation you persist doesn&
28.
by kpmah 6y ago
The problem with a narrow OO mindset is that it encourages encapsulation and atomic objects with hidden state. Simply gluing those pieces together can create suboptimal representations - a more holistic thought process is better.
29.
by kpmah 6y ago
I think you are vastly overstating the risks of changing requirements. It is usually easy to go from a less permissive model to a more permissive one, but the opposite is often difficult.
30.
by kpmah 6y ago
I also experiment a lot with structural editing. My latest project is an editor for a lisp-like language for building small audio synth programs: http://kevinmahoney.co.uk/ocellator/ Hazel looks fantastic - I don'

More ›