rednafi

8 ms·

121.
Test State, Not Interactions(rednafi.com)
2 points by rednafi 1y ago|0 comments
122.
Don't Let Your Mocks Mock You(revontulet.dev)
2 points by rednafi 1y ago|0 comments
123.
by rednafi 1y ago
I like the problems that Protobuf solves, just not the way it solves them. Protobuf as a language feels clunky. The “type before identifier” syntax looks ancient and Java-esque. The tools are clunky too. protoc is full of gotchas, and for s
124.
by rednafi 1y ago
What clicked for me is: A span is a key-value attribute about some point in time event A trace is a DAG of spans that tells you a story about some related events
125.
by rednafi 1y ago
Do you run your changes in the original location? The canonical workflow is this: you run chezmoi cd and make changes there first. Only then do you run chezmoi apply to propagate the changes to the original location. The source of truth is
126.
by rednafi 1y ago
Sometimes a well-designed, purpose-built tool can replace so many kludgy solutions. This doesn’t solve the problem of reinstating the dotfiles to their original positions in a new machine. I’ve tried everything from raw git to gnu stow to m
127.
by rednafi 1y ago
Yes. My workplace soft-enforced it as well. I like using LLMs, but sparingly. I consider myself a better writer and find their tone bland and lifeless. Other than some minor proofreading, I almost never use them to generate text. For coding
128.
by rednafi 1y ago
For most write-ups, I’ve switched to en-dash flanked by two spaces these days. Easier to type and looks less gippitified imo. > But British usage - instead - uses spaces, so an en-dash or an em-dash is acceptable.
129.
by rednafi 1y ago
Yep, vertical scaling goes a long way. But it’s not compute where the bottleneck for scale lies, rather in the resiliency & availability. So although a single server goes a long way, to hit that sweet 99.999 SLA, people horizontally sca
130.
by rednafi 1y ago
Every refactor attempt starts with the intention of 100% coverage. No one can predict how efficacious that attempt will be from the get-go. Eventually, often people find out that their assumptions were too naive or they don’t have enough bu
131.
by rednafi 1y ago
Man, who hurt you? I certainly don’t agree with everything Sean says and admit that “picking the most important work” is a naive thing to say in most scenarios. But writing Python in production is trivial. Why would anyone lie about that? C
132.
by rednafi 1y ago
The SoA and the team structure often worsen this. If your service consists of AWS S3, SQS, MSK, and Kinesis, then you'd have to invest quite heavily in the local setup to make sure everything still works and that the majority of the te
133.
The Cost of Slow Feedback Loops(revontulet.dev)
5 points by rednafi 1y ago|3 comments
134.
by rednafi 1y ago
I understand why they didn’t choose Germany: they didn’t want to buy the GPUs in cash and send the receipts via Fax.
135.
by rednafi 1y ago
All the devops I have encountered so far have been “sysadmin in a trench coat.” Most couldn’t write anything beyond basic Python and Shell scripts. It was mostly ops folks jumping into a fancy new title. So every time something would go poo
136.
by rednafi 1y ago
Most of the DevOps folks I’ve encountered, unfortunately, couldn’t code much. So it was mostly ops work with a fancy new title. The idea of a single entity being responsible for development, operations, observability, and support is flawed
137.
by rednafi 1y ago
Sums up European tech in general. Moving to Germany from the US made me realize how broken basic things are in Europe overall. But I was told Germany has it the worst, and it’s a bit better in other places. I’ve encountered similar issues b
138.
by rednafi 1y ago
Software programming used to be a blue-collar thing in the early days, when hardware wiring was all the rage. Then it became hip, and people would hand-roll machine-specific assembly code. Later on, it became too onerous when CPU architectu
139.
by rednafi 1y ago
I’m reading the comments and thinking: only the HN crowd could get so worked up about something so trivial.
140.
by rednafi 1y ago
This. Convincing a bullshit generator to give you the right data isn’t engineering, it quackery. But I guess “context quackery” wouldn’t sell as much. LLMs are quite useful and I leverage them all the time. But I can’t stand these AI yapper
141.
by rednafi 1y ago
I really don’t get this rush to invent neologisms to describe every single behavioral artifact of LLMs. Maybe it’s just a yearning to be known as the father of Deez Unseen Mind-blowing Behaviors (DUMB). LLM farts — Stochastic Wind Release.
142.
by rednafi 1y ago
I understand the sentiment as I feel the same about Rust. I’d rather raw dog C++ than touch Rust. Doesn’t make sense and I could come up with some BS like you did and make my case anyway.
143.
by rednafi 1y ago
Who said that? Go is pretty amazing to whip up great CLIs quickly.
144.
by rednafi 1y ago
Python and NodeJS bring a whole lot of other problems. But yeah at a smaller scale these languages are faster to work with. At the same time, I have worked at places where people had to rewrite major parts of their backend in other language
145.
by rednafi 1y ago
JavaScript was never designed for non-browser usage. It’s the community’s unquenchable thirst to use the same language everywhere that brought us here.
146.
by rednafi 1y ago
> The rust type system allows, in many cases, APIs that you cannot use wrongly, or are highly resistant to incorrect usage, but to do that requires careful thinking about I need none of that guarantee and all of the compilation speed alo
147.
by rednafi 1y ago
Sounds like the guy who wanted to write curl in a weekend. /s
148.
by rednafi 1y ago
This is true. I have been writing Go for years and still think channel is a bit too low level. It probably would've benefited from a different layer of abstraction.
149.
by rednafi 1y ago
Runtimes like Bun, Deno, or type systems like TypeScript don’t change the fact it’s still JS underneath — a crappily designed language that should’ve never left throwable frontend code. None of these runtimes make JS anywhere even close to
150.
by rednafi 1y ago
Java absolutely does not fill in the niche that Go targeted. Even without OO theology, JVM applications are heavy and memory intensive. Plus the startup time of the VM alone is a show stopper for the type of work I do. Also yes, Java isn’t

More ›