antran22
This is pure corporate slop feels good bullshit generated by an LLM. “critical” comes from “kritikós” which means “related to judgement”. “Akritai” comes from “akron/ἄκρον” which means border.
To be fair the article doesn’t sit well with me on its own, but making crappy, etymologically-untrue claim? Not on my watch.
[0]: https://lore.org [1]: https://news.ycombinator.com/item?id=48571081
The guy is not a software/embedded engineer. He's a bike engineer. He doesn't want to code more than needed to get his idea working. As for reverse engineering, he did plenty of it. He soldered the serial interface into the board, fired up a serial terminal, watch the output & note down the data sent through the wire for each event on the bike. Two things he used LLM for: - Work through the decompiled app & find the commands for controlling the bike - Write an app to run on the CYD.
What would be the things he would have needed to do face if he had somebody work on this project instead of Claude: - Find somebody in his close vicinity, and have him over the workshop everyday, because this project requires access to the hardware. - If he instead found somebody else with another Revo bike, they would have to collaborate really closely & replicate what each other have found to the other person's setup. All that for a vanity, 1-person project?
Kudos to Seth for cracking the control on the bike, just so we can reclaim control of an appliance that we paid for with our own money, one that won't work because the maker can't be arsed enough to make it work without a mobile app.
Related: Cory Doctorow's [Unauthorized Bread](https://arstechnica.com/gaming/2020/01/unauthorized-bread-a-...)
Liquid glass should be taught in design school as an example of what not to do when you design UX. And also in business school as a case of how middle management can fudge up something that is working normally in the illusion of progress.
I'm sorry to say this, but this whole thing reeks of vibeslop, and not just the code. The docs, the readme, even the replies of OP are at least Claude-assisted, if not fully Claude-generated.
And I'm trying not to be derisive about LLM generated output anyway. LLM generated output can be sane and meaningful and to the point. This is just a questionably-cool tech demo dressed up under a sensationalistic title.
Multi-modal models that can understand visual input do exists, but no such visual reasoning process happened in the example you mentioned. Not unless you have a visual feedback loop in the coding harness.
I'm not dismissing the capability of "predicting the next word" however. The vast amount of training data enable extremely complex and useful behavior you just described.
The author used a BlackBerry trackpad. In his blogpost he showed that it can be mounted on top of a keycap. I believe that you can 3d print a special keycap integrate directly with the trackpad.
People who understand tech keep an axe next to their toaster.
Honestly, people have been complaining about Apple's decision on every semi-Apple-related forum forever. Still didn't prevent them from rolling out Liquid Glass. Not sure another one would do the job
As an instance, I had an interview with a CEO of a consulting firm. He took the interview while on the metro, so half the time on the call I couldn't hear what he said at all. When the call ended, I send a message to the HR person giving quite a critical feedback and stopping any further process with the company. A few months later I talked with one of my friend who worked there for 3 months. The CEO and the legal department overlooked some certain paperworks with regard to employment insurance, and when the taxman came and gave them a heavy fine, they hide the situation from everybody until the situation became unfixable. The company went bankrupt essentially overnight and most of the employees has a 1-year plus insurance gap with no practical way to sue for it back.
Moral of the story: if the interview feels wrong, email them and decline going forward right away. Give yourself the satisfaction of consciously dodging a bullet.
The essence of what this page is stating is: “do not act as a reverse proxy between me and a LLM.” That’s rude and shows that the person in question is acting like a brainless automata.
You won't prevent people stabbing others with knife by banning knife or asking people to wear knife-proof vest going outside. You deter them by making everybody know that the consequence of harming somebody else is going to be a very unpleasant experience.
I'm assuming you are much more conscious about this issue than I am (that's fine btw, people have various levels of germophobia) , but practically my whole office block do this without any noticeable health epidemic.
Also standard coffee shops (the Starbucks kinds) always have industrial scale utensil washers that rinse boiling water/UV radiate the utensils. Assuming a government issue the appropriate law, the coffee shops will be able to ensure your container hygiene just fine.
The biggest scam is the paper straw. You still need a certain plastic liner, otherwise the straw will melt down in 3 minutes from direct contact with liquid. The amount of plastic you reduce is penny-on-the-100-bucks-note comparing to the amount of plastic waste produced by industrial activities.
The only way to fix the single-use container problem is for governments to ban it. Either the customers bring their own/rent the shops' containers for take away, or drink their beverages in the shop.
Is this doable? I guess. AFAIR the EU are experimenting with laws around this. Plastic bags ban is already visible in many country, even in non-first-world countries.
I agree that there's a problem with searching today. The line between actual meaningful content and spam is blurring, all the meaningful indicators of the olden days to distinguish between good and bad contents are now gone/unreliable (polished proses, author's reputation). The signal/noise ratio is decreasing.
The approach to improving SNR should have been reducing/eliminating noise (flag spam sites, reputation system) and boost signal (also maybe reputation system, whitelist/blacklist). It's a hard problem simply because of entropy — the more content you have on the internet, the more random it will all seems from the top down.
I'm not saying I have the answer to this problem, I'm really just a noob when it comes to data science. I'm just thinking that mixing a bunch of text together and let a statistical model rehash that pile of grub into a professional, vindictive sounding response will *not* help providing users with enough signal to make sense of what they are looking for.
I know a startup of my acquaintances that have been running on AWS for 5 years straight without paying a single dollar to AWS. When the credits almost run out, they started to migrate their data over to another account with credit. That happened twice already.
It helps to have a portable, replicable IaC config. But also this is sustainable because they are a pretty small struggling shop. You will probably not be able to do this if you are trying to maintain more than 3 nines for an enterprise client.
But most likely, it's just automations in place without an appropriate human override coupled with gross negligence.
- Protect the PR submitting feature behind some CAPTCHA
- Give repo owners some way to manage external contributors, instead of forcing them to do hack like this article
Just move to Codeberg, src.hut, or Gitlab even. Serious contributors will go there with you, the lazy people with LLM farming Github karma probably won't.
It is surprisingly very durable and maintenance-free even for a script kiddie like me to maintain. My advice is (at least when it comes to Vaultwarden) don't think too much about this, just selfhost it, at least for yourself. You'll probably be able to manage it when something happen.
I'm not particularly worried about Bitwarden going belly up because it has already have such a well-established open-source replacement. The worst-case scenario is that Bitwarden make the clients incompatible with Vaultwarden, and like how OP already mentioned in the post, somebody in the community will fork them as soon as this happen.
To be fair plopping a `div` everywhere started way before Tailwind. I blame React and the mess that is CSS in JS for this.