HN user

tansan

155 karma
Posts4
Comments62
View on HN

The definition is broad and can include testing. Refining requires you to review the code for iterations.

Vibe coding (or vibecoding) is an approach to producing software by using artificial intelligence (AI), where a person describes a problem in a few natural language sentences as a prompt to a large language model (LLM) tuned for coding. The LLM generates software based on the description, shifting the programmer's role from manual coding to guiding, testing, and refining the AI-generated source code.[1][2][3]

https://en.wikipedia.org/wiki/Vibe_coding

I enjoy it, but I enjoy what the product enables me to do more than the process; It's a means to an end for me and the process is great, but it gets tedious after more than a decade of it.

I also like cooking, but I like eating more than the actual cooking. It's an means to an end, and I don't need to always enjoy the cooking process.

Vibe coding is pretty broad and is a spectrum

Vibe coding (or vibecoding) is an approach to producing software by using artificial intelligence (AI), where a person describes a problem in a few natural language sentences as a prompt to a large language model (LLM) tuned for coding. The LLM generates software based on the description, shifting the programmer's role from manual coding to guiding, testing, and refining the AI-generated source code.[1][2][3]

https://en.wikipedia.org/wiki/Vibe_coding

https://en.wikipedia.org/wiki/Vibe_coding

Vibe coding (or vibecoding) is an approach to producing software by using artificial intelligence (AI), where a person describes a problem in a few natural language sentences as a prompt to a large language model (LLM) tuned for coding. The LLM generates software based on the description, shifting the programmer's role from manual coding to guiding, testing, and refining the AI-generated source code.[1][2][3]

This sounds like a boomer trying to resist using Google in favor of encyclopedias.

Vibe coding can be whatever you want to make of it. If you want to be prescriptive about your instructions and use it as a glorified autocomplete, then do it. You can also go at it from a high-level point of view. Either way, you still need to code review the AI code as if it was a PR.

Market caps aren't cash.

It's an odd comparison and is dishonest to minimize the payment through a speculative value that the market decided on. If Apple owned 50% of the shares and sold all their shares today, they would not be getting 50% of that $3T because of market forces.

RTO initiative seemed more like an attempt at value extraction more than anything else.

Buildings have mortgages, surrounding businesses need to be supported, etc... Local economies dipped and some hedge fund portfolios suffered, and RTO was the only way to pump their bags.

This is all conjecture

I'm asking for any material that supports this statement: "businesses realise that regular time off (and as much time as you need if ill) increases happiness and therefore productivity."

Productivity can be measured and if that productivity was increased then those statistics should be more visible!

I would love to have a 4-day work week.

It's a more grown-up arrangement where businesses realise that regular time off (and as much time as you need if ill) increases happiness and therefore productivity.

Is there a metric of some sort that I can share with other people that demonstrates 4 weeks PTO does work and has led to increased productivity in Australia?

I personally believe in shorter work weeks, but my experience is anecdotal, so was wondering if there was a study or some kind of economic metric that reflects that statement for increased productivity in AU.