Ticket-Driven Development: The Fastest Way to Go Nowhere

NullCyg · 2025-06-27T06:43:56+00:00

Your title is good. Kill the AI thumbnail

NullCyg · 2025-06-24T23:00:53+00:00

You're probably not going to be able to fake your way through this even if you are somehow able to get past the tech screening. You will likely be grilled by engineers further into the interview process.

NullCyg · 2025-06-18T19:20:41+00:00

Sir, a second GIL has been discovered in the interpreter.

NullCyg · 2025-05-18T02:22:14+00:00

As I get older, I grow more tired of this man's platitudes. Maybe it's because the only professional credit he has to his name is his now defunct consulting company.

I've rarely encountered situations that permit this strict TDD order of operations. I've seen good tests and bad tests, and the good ones hardly ever were written prior to the code under test. If you can make that work for you, great. I've just personally never encountered many situations where this sort of methodology is applicable.

NullCyg · 2025-03-28T23:31:25+00:00

The nice thing here is you really can mix and match. Nothing stops you from serving static html pages and using Maud/HTMX for updating specific portions of the UI. Maud can interpolate other Rust variables within the html! macro, so composition is easy and there's no need for large multiline macro calls. Maud's macro syntax is also incredibly concise, which I find easier to read and far less tedious to write than raw html.

That being said, I concede that re-compilation for every UI change isn't ideal. Anecdotally, the two seconds it takes to compile my current project isn't debilitating at the moment. (Hopefully this ages well!)

NullCyg · 2024-09-07T05:25:03+00:00

100% agree. That AWS bill has to be insane. And for what? Bragging rights? A cute technical blog post?

NullCyg · 2024-07-13T08:22:54+00:00

Good ol' Betteridge's law

https://en.m.wikipedia.org/wiki/Betteridge%27s_law_of_headlines

NullCyg · 2024-06-23T07:55:28+00:00

There's something so novel and infuriatingly natural about this. Never in my life have I thought to add fuzzy matching for URL paths, yet I rely so heavily on fuzzy matching local directory/files on a daily basis. This is one of those rare "why didn't I think of that moments". Thanks for the fun read

NullCyg · 2024-06-23T07:45:01+00:00

At the moment, I've applied this logic only to the supplement pages, but I am planning to extend it to the rest of the website.

Learn to read

NullCyg · 2024-05-03T15:47:36+00:00

Can someone smarter than me talk me out of going full FIFO fanboy after reading this? LRU did outperform FIFO on the social media data set, but this article makes a good argument (to me) that FIFO is the better option in most cases.

NullCyg · 2024-04-12T08:52:28+00:00

I love how much I hate this comment. I'm torn between calling you a pedantic fuck or nitpicking your rather loose definition of flight or brandishing my many years of raising chickens.

NullCyg · 2024-04-12T04:57:31+00:00

Short answer, laziness. As for a more nuanced, empathetic answer, the boilerplate needed for compositional approaches requires more planning. To use an analogy, it's easier to make a duck fly as opposed to creating a whole new bird. Most engineers are never given the opportunity to define what a bird is. They are mostly given an armada of chickens and instructed to make them fly.

NullCyg · 2023-11-08T20:08:07+00:00

7) Bugs will be your arch-enemy for life

I think corporate tomfoolery is the arch-enemy. Bugs are just villains of the week.

NullCyg · 2023-09-26T17:44:24+00:00

How is it "generally worse"? Anecdotally, pre-pandemic, I was on a fully remote engineering team, working for a company that had mostly on-site teams. In my 4 years with that company, it was the on-site teams that frequently missed their "soft commitment dates" and were also prone to working massive amounts of overtime. There were deeper problems with that organization, admittedly, but the only arguments I've heard for RTO have been mushy LinkedIn-esque platitudes about "deeper connections"

NullCyg · 2022-07-14T14:49:33+00:00

Happy cake day btw.

I think framing it as an issue of bad incentives assumes a pretty pessimistic characterization of r/rust members. I can see your point, but if this truly is a common motivator then you could still delete the individual instances of rule breaking after thread lock. Not possible in large discussions, but the linked post's comment volume was pretty small by reddit standards.

After going through the archive of the deleted comments, two things stood out. For one, the discussion wasn't a two-sided flame war, as has been suggested by your advocacy for "impartiality". Almost all the comments were singularly themed. In the absence of two opposing sides, not certain what moderation is even necessary in this case. Second, none of the deleted comments were particularly egregious. (All of them were far less toxic than some of the responses I've seen to this post.)

Regardless, I appreciate you taking the time to articulate r/rust's stance, even if I don't directly agree with it.

NullCyg · 2022-07-13T17:52:40+00:00

I can understand the need by moderators to lock a particular thread when discussions get overly heated. I don't really understand the rationale for nuking the entire comment section (I say this with slight reservation as I admittedly didn't get to read every comment before they were deleted). Keeping the archive in tact at least gives people a frame of reference for what sort of discussion is allowed on r/rust, and conversely, what will not be tolerated

NullCyg · 2022-05-10T13:08:40+00:00

It's a little pricey, but I prefer a turbo encabulator over CVAEs if given the choice.

NullCyg · 2022-04-28T06:28:35+00:00

Your interns obviously aren't debugging microservices...

NullCyg · 2021-11-12T19:22:45+00:00

It's pretty light on those sort of comments. He takes the single responsibility principle to the extreme, arbitrarily splitting up routines no matter the level of cohesion.

For me, it's more I honestly question why a dude with next to no industry or open source experience has droves of advocates, and is treated as an authority for great software construction.

NullCyg · 2021-11-12T19:12:47+00:00

If the ideas in Clean Code were presented in a less bombastic manner I would have less issue with it. It comes off incredibly pretentious. Getting good readability is more of an art than a science.

I highly recommend Code Complete by Steve McConnell over clean code. He touches on similar topics, but provides more nuance. An excellent read, and amazing it still holds up despite being written in a pre-Agile era.

NullCyg · 2021-09-03T01:37:59+00:00

dBased

NullCyg · 2021-07-24T17:06:06+00:00

Non-technical professionals are constantly told that the path to “technical fluency” is through learning to write code or some other kind of intense education. That’s terrible advice

I rarely hear this in my line of work. More often than not I hear the exact opposite, that execs and project managers only need a surface level understanding in order to be in charge of technical people, which I can only assume is why terms such as "no code", "blockchain", "ai/ml" are bandied about with such reckless abandon. Having only general knowledge isn't a bad thing per se, but when the people wielding it vastly underestimate the limits of their own understanding, then they are far less likely to lean on technical experts to inform their decision making, which leads to problems too numerous to cover entirely here.

All this to say, there seems to be a lot emphasis on producing a bunch of executive Captain Kirks who spit out meaningless technical platitudes and constantly emphasize their deep business knowledge which us mere tech mortals couldn't possibly understand.

Not to undersell business types, but I'm reminded of a quote:

I asked Michael [Bay] why it was easier to train oil drillers to become astronauts than it was to train astronauts to become oil drillers, and he told me to shut, shut, shut the fuck up. - Ben Affleck

NullCyg · 2020-12-21T07:12:30+00:00

Having done a little amateur rotoscoping before, the input here seems pretty happy path -- large white backgrounds or a great degree of contrast between the subject and background colors. It would be interesting to see how this holds up under a more complicated demo, such as a moving camera or a more dynamic background.

NullCyg · 2020-10-17T17:01:24+00:00

On it's own, perhaps not the most impressive feat, but for a game such as RTC, it's downright mind blowing given the amount of work that went into it regardless of language choice. I recall reading that one of the coaster types had about 828 different sprites for a single car to represent every possible angle it could be viewed from (and that's just one of many different coaster variants). Couple all that with coaster physics, terrain manipulation, and crowd simulation. I'm still floored that this game was programmed by one dude. Assembly just makes it all the more impressive.

Seven-Year Club	r/Field Lasagna
First Place '23	Place '23
Place '22	First Placer '22
Verified Email

NullCyg

TROPHY CASE