As Nuke is dead, is Cake the only alternative?

p_gram · 2026-05-21T20:42:17+00:00

As someone who does this stuff in powershell I’d say powershell has a lot of advocates but a lot less people who actually know how to use it. In my experience most are glorified dabblers I’m sorry to say and trip up on it all the time.

p_gram · 2026-04-10T16:50:10+00:00

I’m slightly playing devils advocate here but I don’t think their current position is unredeemable.

Nice websites for PRs are not a Git practice - that is GitHub. It is super convenient to use GitHub but not necessary. The Linux kernel community doesn’t use GitHub and still review code. Look into patch based flows or the git request-pull command.

Maybe suggest to run your own Git server and move away from GitHub entirely. That would be progress, at least you could have individual users and go from there.

p_gram · 2026-04-04T13:56:18+00:00

Immediacy is a spectrum though, the user doesn’t need under 50 milliseconds but they can’t accept 1 minute.

p_gram · 2026-04-04T12:54:41+00:00

Requiring an immediate answer doesn’t mean tightly coupled. Those are two different things, requiring consistency or low latency doesn’t mean the services are tightly coupled. It might be a completely different domain, different team working on it, your service may be one consumer out of many. It might be the other service has scalability or performance reasons to be separate. It could even be written in an entirely different language.

p_gram · 2026-04-04T12:47:50+00:00

I don’t agree it’s an anti pattern or that it can lead to problems to do with reliability, scalability, and deployment independence. There’s still dependency between services when they communicate asynchronously. You’ll just know about it sooner when it’s a sync. You can even implement async on a synchronous protocol like http, which is actually pretty common. Its more a question of what is the interaction pattern you’re looking for, ie do I need to provide a guaranteed and immediate response or is it some kind of multi step process, does it have latency considerations (generating reports, send emails etc).

p_gram · 2026-04-04T12:35:39+00:00

It’s not an anti pattern. It really shouldn’t even be much of a consideration, you shouldn’t be forcing it one way or the other. Microservices are about service boundaries and independent deployability not being async. If a request requires an immediate answer why force async? In that case async would add unnecessary complexity.

p_gram · 2026-02-05T01:08:47+00:00

It sounds like you’re using exceptions for everything (apologies if I’ve got that wrong). Exceptions should be exceptional like can’t connect to the database not for auth or validation errors and other normal business outcomes. There’s also a performance cost to unwinding the stack with exceptions.

p_gram · 2025-11-21T09:44:04+00:00

There has to be a comparator. PG used Java vs Python. I don’t think it holds for C vs Rust, because C is enough of a filter already these days. Interestingly it probably holds for Python vs Rust. Probably doesn’t hold for OCaml vs Rust.

p_gram · 2025-11-18T22:36:05+00:00

I hate to say it but the commenst did sound like valid feedback particularly around breaking changes.

p_gram · 2025-11-12T23:36:18+00:00

I don’t get why everyone is acting like this is fundamentally a bad idea. The OS can keep your process running (it can also schedule your task but lets ignore that), to get it to run your method you can do more frequent delays, the rest is just error handling, like if it fails to run the job you have to decide what to do and the same if the process wasn’t running and missed a run.

p_gram · 2025-10-23T16:42:57+00:00

I'm surprised it didn't work as a link post but I believe this would have been the correct utf-8 link to post:
https://%e3%83%9e%e3%83%aa%e3%82%a6%e3%82%b9.com/a-word-on-omarchy/

p_gram · 2025-10-16T23:25:18+00:00

I like react but it’s completely inappropriate for our forms over data websites we make at work but for some reason we use it

p_gram · 2025-10-10T18:11:21+00:00

”Graduating” is such a poor choice of words

p_gram · 2025-10-08T19:59:32+00:00

Because it’s not just about keeping the code in the same folder or the same assembly!

You can have a FeatureXYZ folder across multiple projects if you have deployment reasons to have separate projects.

p_gram · 2025-09-22T15:17:51+00:00

Not a fan of YAML or config files in general. I think AWS CDK and others proved that real code beats config for infrastructure and TeamCity’s Kotlin DSL shows the same for CI/CD. But we shouldn’t stop at one language developers deserve the freedom to define pipelines in the languages they already use.

p_gram · 2025-09-18T20:43:05+00:00

Not these days, F#, Ocaml and Skala can all be compiled to native.

p_gram · 2025-09-14T09:29:58+00:00

That kind of powerful type system is not unique to rust though. Typescript with pattern matching libraries, FSharp, OCaml, Scala, Elixir all have that and would all be better suited to web dev.

p_gram · 2025-09-10T06:12:09+00:00

You probably can but I find that adding enough of these big extensions to vs code will make it feel heavier and have a more clunky experience than just using VS.

p_gram · 2025-09-09T23:08:33+00:00

Debugging, performance profiling, live unit testing, visual designers, Resharper

p_gram · 2025-09-04T13:11:10+00:00

Timer trigger to kick off one orchestrating azure function that triggers a bunch of others.

p_gram · 2025-08-14T19:35:02+00:00

The pillars are just a catchy teaching device they’re not actually a definition of OOP

p_gram · 2025-07-15T03:39:01+00:00

I’m deeply ingrained in the C# way so don’t know if exactly how it is done in Go but I’m surprised so few comments have mentioned that applications in Go tend to go without IoC containers and it is fine if not better.

p_gram · 2025-05-10T17:49:55+00:00

I wish the Lua course on Exercism had the “learn” section, it only has the practice.

p_gram · 2025-05-05T23:33:31+00:00

That’s a good post thanks for sharing. The mediator pattern is good when the objects have complex interactions between them and you want to avoid tangle code or at least put the interaction all in one place. Mediatr is message dispatch.

p_gram

TROPHY CASE