What an odd take. It is often titled "software craftsmanship". Is the craftsman not allowed to practice? Not everything needs an immediate real-world application. Not everything needs to be enterprise-grade, bulletproof, web-scale or whatever. It needs to work for the creator, and sometimes not even that.
In the same way we appreciate Japanese wood joinery, why not not just appreciate this? Someone might even learn a trick or two reading it.
> What an odd take. It is often titled "software craftsmanship".
No, not really. This is exactly the opposite example of software craftsmanship. Software craftsmanship involves things like technical excellence in delivering maintainable software that is adaptable to change.
Picking assembly, of all things, for a web server represents a complete failure in the analysis of both the problem and solution domain.
This sort of project is more in line with parlour tricks, juggling, and stunt shows. Trying to frame this sort of project as software craftsman is like discussing the whole Jackass series as cinema next to Hitchcock and Scorcese. It may take skill and practice to be punched in the nuts, but that doesn't make it a craft.
Quite the opposite, in fact. When customs finds that any rule, like the CE declaration on electric devices, is broken, they can and will seize such goods.
You could of course attempt to circumvent or mislead customs. After all, they don't have the capacity to check all imported goods in-depth. That however would usually be a criminal offense.
CE is important, but we're talking about trade regulations, not technical here, so I took a mental shortcut. But you're right. Though effectively all modern products are CE certified. All starlabs need to do is to have that CE stamp and they can ship it to customers in EU without having EU entity.
YAML isn't the problem. It's that every single action is basically curl-to-sudo-bash. Even disregarding the security implications, the ergonomics are truly horrendous. They were with Azure DevOps and they certainly are with GitHub Actions. Bad interfaces, surprising behavior, it's got it all.
CI must only consist of shell commands. No abstractions, no surprises. (Except maybe with PowerShell, where the principle of most surprise rules.)
What do you mean, in 5 years? It's not like everyone just bought a new computer. My gut says it's exactly the other way around: most computers are old. They may fail as soon as today.
That’s exactly what I’ve become. A monkey typing prompts and pressing Enter to confirm plans and actions.
Obviously I am exaggerating but my days shifted from figuring out issues and coming up with solutions to explaining the issue to Claude and supervising the work.
What worries me is two things:
1. Current models were mostly trained on human work. Do we have enough training materials created now for the models to progress or they’ll be training or other models output? That cannot end well.
2. I’ve started as a Junior Engineer and had opportunity to learn and become Senior. The job market for junior is really bad cause businesses plan just for couple quarters ahead. They replaced juniors with AI. Who’s gonna replace seniors? And don’t say AI ;)
Is this a design detail that has changed over time?
I have a MacBook Pro Late 2013 and the top edges on the body are not sharp at all. They are already rounded down, with maybe 0.5 mm radius. It's very subtle. I find that the edges are rather pleasant to the touch.
No, WinGet does not generally protect against this. While PRs to update package versions are verified in some way before going live, the necessary throughput can only be achieved with shallow checks. A determined actor could easily get a malicious update in, once they control the original source.
Other than that, WinGet is mostly just "run setup.exe". It is not a package manager. It's basically MajorGeeks as a mediocre CLI.
Nonsense. WinGet has the ability to add repositories, just like any other package manager. If you want the 'approved' packages for the distro, that would be the msstore repository. If you want to use the 'community feed', which WinGet warns you about the first time you use it, it's less vetted, but still goes through Defender scans and community moderators.
If you go adding any old repo to APT, you have the same risk. You should look at how much code review goes into packages for major distros like Debian, hint, not much, especially once the initial package was accepted.
Dunno what they’re trying to build, but I encourage everyone to try what they already have built. It helps me work on multiple changesets in parallel. This often just happens, for example you work on something and discover a bug in something else that needs to be fixed. In GitButler, I can just create another branch, drag the changes in there, push and done.
Also, if you ever worked with Perforce, you might be familiar with changelists. It’s kind of like that.
Now, GitButler is by no means perfect. There are many rough edges. It tends to get stuck in unexpected states and sometimes it isn’t easy to rectify this.
It also cannot split changes in a single file, which is a bummer, because that’s something I encounter routinely. But I understand this complicates the existing model tremendously.
In the same way we appreciate Japanese wood joinery, why not not just appreciate this? Someone might even learn a trick or two reading it.
reply