Eager Eagle

flake8-simplify has a bunch of rules like that for Python, most of which may be automatically fixed if you’re using something like ruff, so you never have to spend time actually fixing it.

no you didn’t get the job

but the CEO position is yours if you want

https://github.com/TimefoldAI/timefold-solver

It depends on the context. If it’s an URL that is easy to guess and reflects user-created content, your system is leaking information about their users if it returns 403. The example that comes to mind is GitHub returning 404s for both nonexisting and private repos when the authenticated user doesn’t have access to it.

implementation without design

and to just send “Bad request” when it’s a good request - does not make sense

That’s when you use a 5xx status, then. The client doesn’t care how many other services you reach out to in order to fulfill their request. A 5xx code also covers failures in other parts of the system.

A 2xx means success to its requester. If you have an error in step 6 out of 13 that breaks the resource action, you shouldn’t be returning a success.

You might argue what to return and what kind of information to include in the response (like tracking numbers), but it shouldn’t be a 2xx and I don’t see how a misleading 200 would be more helpful than a 400 bad request.

That’s not what HTTP errors are about, HTTP is a high level application protocol and its errors are supposed to be around access to resources, the underlying QUIC or TCP will handle most lower level networking nuances.

Also, 5xx errors are not about incorrect inputs, that’s 4xx.

hey, at least it’s not a 200 with { "error": "Bad request" }

if this is real, that’s the kind of people who should be worried about being replaced by an ai

it’s also Claude

lmao

deleted by creator

shitty Merge PR from patch1 that people seem to use

One of the reasons I hate merge commits and just force linear history on the repos I control.

god, I already struggle trying to find information in github issues, I can’t imagine using email for this

yeah, trying to convince our product owner to read commit messages wouldn’t go smoothly in my team. Some of them love their tickets…

the dependency to the issue system is unfortunate though, I do miss a “decentralized issue system” doing what git does for version control that would just seamlessly integrate with git and have a nice web GUI for less technical folks.

I just keep my commit messages one-liners and elaborate more on pull requests, where there’s enough context to really justify the change.

this probably won’t change anything for end-users, but transpiling 1.5M LOC from TS in 5.7s is pretty impressive.

Plot twist: Dave had cheat sheets for previous projects glued to the ceiling

sure, you can store the config in $XDG_CONFIG_HOME/your-app-name/ (the var usually defaults to ~/.config/).

What does a staff engineer do? Engineers staff?

drops rubber duck