Please take care that modern design practices and the latest materials are used in construction of the house, as I want it to be a showplace for the most up-to-date ideas and methods. Be alerted, however, that kitchen should be designed to accommodate, among other things, my 1952 Gibson refrigerator.
That’s actually too easy, because electrical systems have been standardized for a long time.
Should be something like “15 highpowered electrical stoves, but keep the total power consumption below 15 Watts.”
Or, homeautomation and integration with google/alexa, but using the old fridge.
Who would've thought a sector with gold flowing through its hands would be so stingy when it comes to updating their backend that they'd end up relying on a dying language, and call upon AI to update it for them rather than just paying a competent team to create and rigorously test a new backend in a modern language
One problem is that they need to put a price tag and therefore a timeline on such a project. Due to the complexity and the many unknown unknowns in theses decades worth of accumulated technical debts, no one can properly estimate that. And so these projects never get off and typically die during planning/evaluation when both numbers (cost and time) climb higher and higher the longer people think about it.
IMO a solution would be to do it iteratively with a small team and just finish whenever. Upside: you have people who know the system inside-out at hand all the time should something come up. Downside of course is that you have effectively no meaningful reporting on when this thing is finished.
TypeScript of course. The compiler often times catches mistakes in variable names, API methods, whatever. So it saves time by not having to run the whole application all the time. Also the input help is much better, when the editor knows sth is a string or a number, for example.
I absolutely do. Spreading the idea that news sites are all propaganda and the only entities involved in this kind of practice is, in itself, propaganda.
Infowars tells you Nazis are something you disagree with? Haven’t heard from them in a while. Would have thought they’d quietly drop the Nazis are evil thing.
There’s a lint rule that looks for @nocommit in all modified files. It shows a lint error in dev and in our code review / build system, and commits that contain @nocommit anywhere are completely blocked from being merged.
(the code in the lint rule does something like “@no”+“commit” to avoid triggering itself)
Neat idea. This could be refined by adding a git hook that runs (rip)grep on the entire codebase and fails if anything is found upon commit may accomplish a similar result and stop the code from being committed entirely. Requires a bit more setup work on de developers end, though.
Would a git hook block you from committing it locally, or would it just run on the server side?
I’m not sure how our one at work is implemented, but we can actually commit @nocommit files in our local repo, and push them into the code review system. We just can’t merge any changes that contain it.
It’s used for common workflows like creating new database entities. During development, the ORM system creates a dev database on a test DB cluster and automatically points the code to it with a @nocommit comment above it. When the code is approved, the new schema is pushed to prod and the code is updated to point to the real DB.
Also, the codebase is way too large for something like ripgrep to search the whole codebase in a reasonable time, which is why it only searches the commit diffs themselves.
At my workplace, we use the string @nocommit to designate code that shouldn’t be checked in
That approach seems useful but it wouldn’t have prevented the PyPI incident OP links to: the access token was temporarily entered in a .py python source file, but it was not committed to git. The leak was via https://docs.python.org/3/tutorial/modules.html#compiled-python-files which made it into a published docker build.
Not just for credentials, there are many times where I change a setting or whatever and just put “//TODO: remember to set it back to ‘…’ before commiting”. I forget to change it back 99% of the time.
PRs? Isn’t the point of @nocommit that something does not get committed, and therefore no credentials are stored in the git repository? Even if the PR does not get merged, the file is still stored as a hit object and can be restored.
I mean, presumably there’s a microcontroller in this radio. For programming that, your only real mainstream choices are C, C++ and Rust, since you can’t have a language runtime without a filesystem.
But yeah, it’s neither the case that Rust is overwhelmingly popular for that (C/C++ do stick around still), nor is it the only discipline where Rust shines.
Like all sayings, there is context for moving fast and breaking things.
The saying means that when creating something new for profit, don’t worry too much about trying to figure out all the details beforehand and figure it out as you go. This will inevitably cause things to break, but being able to quickly fix that when it happens is the same skills needed to create new features as you go.
The saying does not work with large and complex established systems where breaking things wreak havoc.
It also feels like they chase the “break things” part as if not breaking stuff is a bad thing, and like we should be proud of them for releasing broken and poorly tested updates.
Move fast, break things, fix the broken things, push update/product whatever. They keep forgetting the third step.
Like the startups that ‘disrupt’ the established system by ignoring laws and breaking the parts that worked and selling it like an improvement.
‘Ride sharing’ (unregulated cabs) was only cheaper because of investor funding allowing them to undercut on pricing, abusing the concept of contract workers, and the companies ignoring laws. That isn’t ‘disruptive’ by being innovative, that is cheating the system.
And that’s exactly it. Capitalism rewards having money and how you get it isn’t important. It doesn’t breed technological innovation but it sure as shit pumps out new, fun ways to spew propoganda and avoid laws! And oh boy is paying employees well not even close to a metric by which to measure a successful company.
It’s the least people clever in the room having the volume to make sure that no one smarter than them can speak and then claiming they’re geniuses when only their idea gets through.
I think there is another aspect that is important: limit the blast radius. Shit inevitably happens when you create something new and complex, and when it does, you’d rather minimise the impact where possible.
Or at least a sorta-wealthy family, and the further “foresight” to be in the exact right place at the right time.
That’s the background of most of the Western ultra-rich, just as a consequence of there being vastly more sorta-wealthy families than already ultra-rich ones. Some of them are bound to stumble into situations that add a digit or two to their net worth. For an example, Elon Musk is notable for being tangentially involved in a huge success like three times, despite being a well-known moron.
One project I worked on had 10 different languages. That was rough. But even your basic full stack web application is usually 5 languages: SQL, a backend language, HTML, CSS and JS. Usually some wheel reinventing frameworks thrown in for good measure. 5 languages is light these days.
I work in Java, Golang, Python, with Helm, CircleCI, bash scripts, Makefiles, Terraform, and Terragrunt for testing and deployment. There are other teams handling the C++ and SQL (plus whatever dark magic QA uses).
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.