antran22

Unrelated: the frontpage says: > the root of the name [Akritai] is the same word that gives us critical — which is exactly the software this effort exists to defend.

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.

Now instead of making the comparison with an automatic lawnmower, what would you say if I use your argument when you let a roomba vacuum your room unsupervised instead of asking the neighbor kid to sweep it a broom? This is why it is going to get real philosophical if we want to judge how lazy a person is based on the level of delegation he put on a tool.

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?

Imagine after mowing your own lawn with a petrol-powered lawnmower, you got some shades from the neighbors for "Robbing the kids in the community a chance for some honest labor. If you don't know how to use the gardening shear, ask the kids to do it instead of using the automatic lawnmower. Would be a win-win for everybody".

Good grief, hopefully in v28 Lemay will also throw away the absolute crap that is Liquid glass. Aesthetically it looks horrible, it slows my iPhone 13 — which never before lagged in all its life since iOS 15 – to a maddening crawl.

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.

<critique> OP keep saying the backend implementation doesn't matter, it can be trivially switched to something other than Github. It's not. The whole app you write revolves around Github's HTTP endpoints. There's no actual provider-agnostic Git operation in the code (for that you need to use isomorphic-git [1]). So a much more apt title for this should be: "Macaroni - a chat UI in a single HTML file that stores messages data in a Github repo" </critique>

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.

Saying that this doesn't use a backend is like saying serverless app doesn't run on a server

It's still predicting the next word. Somewhere in the gigantic dataset that the LLM was trained on, there is a phrase that says "gradient border" being in the vicinity of a CSS code that render the stuff. Therefore when you run it on an inference loop there's a good chance it output that CSS code when you tell it to render a "gradient border"

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.

People who love tech buy superdupersmart loudspeaker that will connect to every computer in their house; and also somehow control their superdupersmart coffee maker so they can have a fresh coffee brewed when some Miles Davis play.

People who understand tech keep an axe next to their toaster.

They already have that, it's the Apple Support Community. Apple still manages to neglect most complaints on the site.

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

Let’s use probabilistic models to find the probability of something being the output of another probabilistic model

I have had my fair share of terrible interview as well. The key thing I learnt is that the interview is an opportunity for me to understand the culture of the company and judge my fit there as well. I know that the phrase "dodge a bullet" is used to death in those kind of situation, but if the interviewer is behaving unprofessionally you can safely assume the people in the company will be unprofessional in a lot more other area.

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.