There's plenty of good hardware outside the Apple world. Heck, whenever I get convinced to try Apple hardware or software, its quirks and obvious glitches put me off. Input lag is the topmost issue. It immediately washes off the "quality" impression. But I understand that Apple users are used to that and don't notice such issues.
LG Gram user here with Debian as a daily driver. Can confirm, maybe not 15h, but I don't think about charging. Plus, it's super stable, not a single crash or hang-up over years. It just works. I hope LG will keep this up and not mess up next iterations of the hardware.
Such "sleep(5)" is actually a milestone in a project, a milestone that marks the beginning of deterioration and the end of architectural changes. I've seen multiple pull requests with "sleep" and similar shortcuts, and worse, I've rewound coding agent context and changes because of such model suggestions. I'm responsible for informing management about the consequences of such shortcuts and why we have to take the correct, often more time-consuming and more expensive, approach to avoid project derailment in the long term. I believe that management picks employees. If they don't trust my judgment, then it's okay for me, but I don't feel obliged to be responsible for the consequences.
As a Linux user, I feel like a different breed here: I'm pretty sure the software I'll be using 10 years from now will be pretty much the same, and I'm happy about that.
Whether it involves FAANG companies or not, a job is ultimately just a job. While it's nice to have such a company on a CV and to gain the experience, it is, in essence, similar to any other employment.
Eventually, you begin to consider the drawbacks, such as the monotony of the work or the exhausting nature of on-calls (which disrupt personal life). Then, an opportunity arises from a former colleague at another company, and the outcome is predictable.
Companies present numerous such inconveniences and actively introduce additional ones. Now, we are faced with mandatory RTOs, along with the continuous tightening of the screws and "cutting fat from the bone" (actual words of my company's CTO). Consequently, employees will depart, and it is often the high-performers who will seek opportunities elsewhere, as they are not afraid of the job market.
Well said. Languages are for implementation, not design. There isn't a single language that connects both. Also, every popular language has multiple patterns that communicate code intentions. We can add to that conventions added by frameworks, companies, and even teams.
In my opinion, there's a lot of unnecessary criticism here. The entire AI field is in a discovery phase, with new ideas, approaches, and methods emerging at many levels, including models and APIs.
Right now, we don't even have a single standardized API for model responses (OpenAI's Chat Completions API is the de facto standard, but it's not formally standardized, lacks reasoning responses, and caching remains unclear, etc.).
So some ideas from projects like this could stick and contribute something new.
I can recommend Vertica: SQL, columnar storage, S3 backed, great extensibility, I could keep going. After several years of working with it, I can say it's my favorite OLAP DB that can be as fast as a transactional DB when handled correctly.
Passkey is a great example of how five kitchen chefs can't make scrambled eggs. Horrible user experience, terrible marketing, no mental model like "your phone is THE key," no tangible or even symbolic presentation of the key.
Nah, we need defined levels like for autonomous driving. Level 5 is live deployment of a change where a business need was discovered by AI, the change specified and planned by AI, implemented by AI, and reviewed by AI. Vibe coding (without reading) would be even lower, as a human is in the loop.
Yes, the term isn't universally defined yet. Also, the number of available tools doesn't help here (e.g., my workflow in Cursor and CC differ). My "vibe coding" is probably different than blog post authors' "vibe coding." At my work, we have "AI in dev" meetings to discuss the topic, the variety of opinions resembles comments here, and we try to boil down where the issue is.
Vibe coding is not a 0/1 skill. LLMs generate code as the prompt says, so when you ask what you want, you get it. If you want a specific pattern or architecture, explicitly ask for that. It works really well when you (not the LLM) drive the development.
Thank you for your comment. People would be shocked at how many hazards they avoid because of those regulations. I'll defend China here a bit, as they are improving (at the cost of competing with other, less regulated countries, the irony).
And the cherry on top: those "cheap" items are heavily subsidized from multiple places, including postal fees. When the local production gets extinguished (and it won't come back easily, as "know-how" people will be retired) those prices will change.
Pro is just a paid demo. I hit the limit all the time on a small project, and I'm not even doing anything weird. The product is still great, though.
At work, we checked out a bunch of options, and almost everyone chose something different, so the competition is though.
Historically, the center of scientific innovation shifted from Europe to the United States approximately a century ago, and is currently showing signs of transitioning towards China.
Long ago, I worked for a contractor company, so my colleagues and I had a lot of interviews to get sub-hired. As we had many of those interviews, we got pretty good at them, and we shared our experiences, knew popular tricky questions (like "swap using [place here any constraint]") and had names for different types of interviews. "Kick in the balls" was one of them, tricky questions which showed nothing, except that somebody solved that particular narrow problem or was already familiar with that question.
Having that experience, I know that the only reasonable interview is an open conversation. What was your last project? What was the architecture? What was problematic? How did you solve that? How did you come up with the solution? And so on. The candidate is relaxed, drinks coffee, and talks. After 1 hour, you know who you're dealing with.
If there's time, a pair coding session is informative. There are many small hints, like using shortcuts, that give away pros.
This is an assumption where competition (as a wide term) does exactly the same and focuses solely on AI. But in reality, competition will scale both in incorporating AI and hiring more to keep up with the market.
There's always a new tech frontier. Like, weaving machines replaced looms, cars replaced carriages, and now it's AI. Each time, we need a new kind of worker. We shouldn't worry about jobs changing or vanishing, but we should worry that we won't learn and teach the new stuff fast enough.
BYD is actually well established. But there are dozens of Chinese car brands right now on the European market, simply, there's too much competition, many of them will leave.
European alternatives are expensive, and half of Chinese no-name brands will disappear next decade (good luck servicing such a car). Regarding Chinese brands, they are crash tested by C-NCAP, not Euro NCAP, and somehow every model gets 5 stars. No, thank you.
I live in the EU and actually like that citizens are more important than businesses. I wish some construction laws were more strictly regulated, such as those concerning housing development. For example, in Poland, a lack of strict regulation has caused horrible new housing plans with insufficient parking spaces for apartments. There are plenty of similar examples.
I started with Repomix as an MCP server plus system prompt to reduce the scope to single packages. However, it still consumed too many tokens (and polluted the context with useless information). I used Gemini, context size wasn't an issue, but it was too expensive. Now I just use Cursor, it has built-in indexing with embeddings (I assume).
I'm using AI for grepping, analyzing flow, finding cross-project dependencies, etc. It provides a significant speedup. But the generated code is mediocre at best. Changes look like patches on fabric, not woven threads. AI generates too much redundant code.
Musk's policies are just a small part of the problem. The novelty has worn off, reliability metrics have arrived (last place in the EV category), and service horror stories are common. Chinese companies have started a wide campaign, but I still see more Teslas than Chinese no-names. People don't trust that they will remain on the market and believe they will disappear sooner or later. In the case of a company car fleet, it is advised to buy a single Chinese car just to test the waters. Skoda, VW, and Toyotas rule.