u/dayumnshit

i still have old software on my computer that i paid for once years ago.

it looks ancient, but it still opens. there's something weirdly nice about that.

AI tools have made me realize how much i miss that model.

I understand why generation is different. every time something gets rendered in the cloud, somebody is paying for the compute. when i'm using image-to-video in DomoAI, credits are part of that side of the workflow too.

that part makes sense to me.

what i miss is the feeling that the tool itself is mine even when i'm not actively generating anything.

I'd honestly be pretty happy with a setup where i buy the basic software once, keep using it for normal work, and then pay separately whenever i need cloud generation.

maybe that model just gets harder once so much of the useful stuff depends on servers.

still, i don't really want another monthly bill just because i occasionally want to generate a few clips.

would you rather pay once for the software and then pay for AI compute as you use it, or does a subscription actually make more sense for this kind of thing?

sat down at a dinner spot today scanned the code on the table and was immediately hit with a giant animated lucky wheel spinning on my phone screen. congratulations you won a free drink coupon if you register with your email.

i am literally starving. I do not want to play a gacha mini game or join a lottery club just to see if you have tomato soup on the menu.

what happened to basic utility. last week i scanned a menuforma link at a food stall and it was literally just the food items on a plain page. zero popups zero floating banner ads zero fake discount wheels.

why are restaurant menus turning into low budget mobile casino games. just show me the food and let me pay.

my company is giving us up to $500 for home office gear, and I’m finally replacing the cheap chair I’ve had since college.

I sit for around eight hours most days, mostly typing with a few long calls mixed in. right now I’m between the hon ignition 2.0, branch ergonomic chair, and nouhaus ergo3d.

The HON seems like the safest long-term buy, but it uses basically the entire budget and has no headrest. branch is cheaper and looks nicer in a home office, though the comments about its firm lumbar support are all over the place.

nouhaus seems like a well-rounded choice. only made the list after I saw their Instagram discount. the headrest sounds useful for calls, but I’m still not sure I want a full mesh seat for eight hours.

Which of these still feels decent around hour six, not just during the first ten minutes?

i'm still relatively early in learning web development. over the weekend, i used AI to build a working, deployed prototype (just a small dashboard with a clean UI) that i previously thought would take me months to even understand. the speed is pretty wild. but once it was live, i got this really uncomfortable feeling:

Am I actually getting better at programming, or am I just getting better at asking tools to temporarily hide what I don’t understand?

it sometimes feels like a beginner can get to a working app in 48 hours that might have taken half a year of traditional learning before AI. you just need a rough idea of what a database is or what an API does, and the models handle all the syntax.

I'm not really worried about the flood of AI slop. Low-effort apps will always exist. My concern is about the roadmap for people who genuinely want to become good engineers.

The AI built a working dashboard for me, but i realized i didn't actually know if my API endpoints were verifying permissions on the server, or if a user could just fetch someone else's data by guessing an ID. If a concurrency issue pops up, or the database starts dropping data when scaling from ten users to ten thousand, i'm completely blind. AI built the 'happy path'. It made getting a working product trivial, but it doesnt make understanding why it reliably works any easier.

And it’s not only Claude Code or Cursor anymore. End-to-end platforms like Replit, Lovable, or Enter Pro are starting to bundle the coding agent, database configurations, and cloud hosting into one workflow. its barely any time to go from a prompt in your head to a live URL now.

i know the 10,000-hour idea is more of a popular shorthand than a law. But it made me wonder: if the problems that once took years to learn, like basic CRUD, setting up auth, writing boilerplate, and deployment pipelines, become BASELINE tasks, does the finish line for expertise just move further away?

If the floor is suddenly this high, what does the ceiling look like now? Does a true expert just spend all their time on complex system architecture, security models, and fixing weird agent hallucinations? Maybe saying it now takes 20,000 or 30,000 hours to become a senior dev is just my anxiety flattening a complicated change into a scary number.

AI might also let us learn faster. i can use it to explain a complex repo in seconds, generate weird edge-case tests, or act as a brutal code reviewer. It could just be that what we need to learn has changed, not that it takes longer.

tbh i'm still feeling a bit lost on how to handle this. For the senior devs in here (especially those of you cleaning up vibe-coded apps):

- is AI actually making it harder to become an expert, or is it just changing the definition of what an expert even is?

- what underlying fundamentals should a junior absolutely not skip today? (like, what's the stuff that will bite me in the ass later if i don't learn it now?)

- how do you use these end-to-end tools without fully outsourcing your brain to them?

- what kind of projects or exercises actually expose the architecture and security gaps in AI-generated apps so i can break them myself?

I requested a Cantonese voiceover, the agent auto-created text-to-speech node but the final video kept mixing Cantonese and Mandarin.

A friend of mine runs a small cafe, and we’ve been going back and forth about why customers keep ordering the same couple of things even though some of the other dishes are just as good.

He thinks people don’t read. I think the page is too crowded. His chef wants photos everywhere. He hates that idea because he thinks too many food pictures make a place look cheap.

So I made three rough versions of the same page and showed them to a small group of regulars and friends. Nothing scientific, just a quick sanity check. I duplicated it in menuforma so I wasn’t rebuilding the whole thing from scratch every time.

The first version had photos for almost everything and barely any text. People chose quickly, but they also ignored anything that didn’t have a picture.

The second had no photos and longer descriptions. A few people liked knowing exactly what was in everything, but most of them skimmed for a while and then fell back on the safest item they already recognized.

The third only used photos for a few signature dishes, kept the descriptions fairly short, and added a small “house favorite” marker to a couple of items.

That version had the strongest effect. People stopped comparing pretty quickly and went straight to the highlighted dishes. One regular basically said, “I figured it was marked as a favorite for a reason.”

What surprised me was how much the presentation changed what people noticed. Same dishes and same prices, but people came away wanting completely different things.

The downside is that once you highlight a few items, everything else can start to look like filler. And I still understand my friend’s concern that photos might make the place feel less polished if they aren’t done really well.

For people who work in cafes or small restaurants: do food photos genuinely lower the perceived quality of a place, or is that mostly an owner preference? Have you found a middle ground that helps people choose without making the whole thing look like a takeout app?

Character consistency kept falling apart after the first few clips, so I stopped changing prompts and tested the reference setup instead.

The five versions were:

one front-facing portrait

front + profile

five-angle turnaround

five angles + expression sheet

character turnaround + expression sheet + location references tied to each storyboard shot.

The biggest jump wasn't between one portrait and more portraits. It happened when the character refs and location refs were planned together.

Same character under a new background or lighting setup would drift way harder when the model had no visual anchor for the scene.

I kept all five tests side by side so I could compare the reference set, prompt, and output for each shot without rebuilding the setup every time.

The fifth setup held best across the sequence, but it still wasn't perfect around profile movement and hard lighting changes.

Anyone getting reliable results beyond 5–6 scenes without training a LoRA?

I ate at a Korean BBQ place in Shanghai recently and the first thing I noticed was the ventilation.

The table stayed busy and there was visible smoke, but it did not hang around my face or settle into my jacket the way it usually does. A Korean friend I know from bcgame jokes that BBQ is half meat and half airflow; this was the first meal where I understood what he meant.

I am not posting the name because this is not meant as a restaurant promotion. I am curious about the setup itself: do the places that handle smoke well here usually use a downdraft system at the grill, or is the hood design above the table doing most of the work?

Kapag lumaki ka sa Pampanga, normal lang na may matinding opinion ang lahat tungkol sa sisig, kakanin, at kung sino sa pamilya ang “tama” magluto.

Ganun din sa gatherings. Kahit simpleng okasyon, may pagkain para sa mas maraming tao kaysa expected, may kwento, may chismis, at may tita na alam na ang update bago mo pa sabihin.

Napansin ko na mas naa-appreciate ko iyon kapag inilalayo ko muna ang phone. Madali akong mawala sa videos, chats, o bcgame at hindi marinig yung ordinaryong usapan sa bahay.

Ano yung maliit na family o food habit na agad ninyong nami-miss kapag matagal kayong wala sa Pampanga?

So I have studied Thai for about two years and will be in Bangkok as an exchange student in Oct. I can handle basic convos, but I often speaks in low pace and don't always catch how indirect an answer is meant to be.

I have read the usual advice about shoes, temples, the polite particles around. I also met a friend there through bcgame, he also warned me that classroom and group-meal etiquette can feel different from tourist situations, but we ran out of time before getting into examples.

So I am mainly asking about university life, like how's yall experience is: joining classmates for food, asking a lecturer to repeat something, splitting a bill, and knowing when a polite “maybe” actually means no. Which small mistake do exchange students make even after reading the basic guides?

I borrowed a cheap micrometer for a small project and kept getting readings that were close, but not close enough for me to stop checking. The thimble also felt different from one pass to the next.

I eventually bought a Mitutoyo. The embarrassing part is that I spent ten minutes checking bcgame between measurements because I did not want to admit I still was not sure whether the tool or my technique was the problem.

The new micrometer repeats much better, but I do not want to treat the name on the frame as proof that every reading is right. What is the normal first check in a shop: clean the anvils and zero it, compare against gauge blocks, or have somebody experienced check my feel?