They often WERE creative geniuses with a digital camera! Brilliant people! In fact they were the ones who came and went the fastest, what makes you useful in industry is very frequently nothing to do with genius or creativity or mastery of the tools. It's things like reliability, stability, team spirit, open mindedness etc.
Creative genius is one game, but it's far from the only, or even, main one.
Yeah same. The idea that you'd be merging code to `main` that isn't ready to deploy is crazy to me, but that doesn't mean you need a `develop` and `prod` branch. The main + 1-layer of branches has generally been totally sufficient. We either deploy to branch-preview environment or we just test it locally.
I'm not questioning your experience, but how "enterprise" is that experience? Gitflow was no small part of my convincing my company to move off TFVC. I doubt they still use, but it was shallow waters for scared folk.
I strongly doubt that my story, just as much as yours, is unique.
I don't quite see the appeal, because Claude Code already supports something similar. They spin up container to make the changes in and then open a PR. I can just use the Claude iOS app to do this. My computer doesn't need to be running or exposed to the internet.
Omnara’s is useful if you have a complex dev setup that’s hard to replicate in Claude’s remote container, or you want to test things out locally without any friction. Omnara tries to make switching between being on your computer and being on your phone feel seamless, whereas in Claude, local and remote dev feel more disconnected.
I've just started using Anki and I'm almost grieving. If I had had this 15 years ago I probably would have done so much better in school. I've always struggled with memorizing, but Anki has made this much easier for me. I started learning Japanese 4 months ago and I'm baffled by how much I've retained in that period. Now I'm playing with using it to learn the rules for the OneRing TTPRG.
> In my experience, if you're working on a green-field project, you're working long hours, making very little visible progress, you have to write a lot of code, make important decisions.
Funny, this is the complete opposite of my experience. Greenfield projects I've been a part of have had a ton of highly visible progress with _frequent_ updates to stakeholders basically from day 1. Same goes for complex additional features.
I've seen both kinds. GF projects where the senior devs feel that they have to get something right from the beginning, spending a year just on that piece (a set of widgets, a data ingestion framework, a state machine that covers the entire underlying algorithm). And other GF projects which have frequent updates and are open to development with very few speed bumps.
Of course you can call out the former examples as incompetent or hubris, and they will probably occur less and less, but nevertheless they exist.
I was going to say the same. In my experience I can say without hesitation green field projects is how you advance your career, become visible and get promoted.
What is progress? Are you sure that was greenfield?
I think the OP meant projects that required long investments without immediate returns. For instance, a platform migration that requires many components to be finished before it can even be tested. Or, real greenfield, like a new product venture with a unproven customer thesis. The kind that requires months of work before you can go to market and validade... How do you report progress? Components built, percentage completed? Without something a user can drive or a seller sell, that's not progress... It's just speculation.
> Half these issues stem from a relative misunderstanding of exactly where the code is running.
I used to think Javascript everywhere was an advantage, and this is exactly why I now think it's a bad idea.
My company uses Inertia.js + Vue and it a significantly better experience. I still get all the power of modern frontend rendering but the overall architecture is so much simpler. The routing is 100% serverside and there's no need for a general API. (Note: Inertia works with React and Svelte too)
We tried Nuxt at first, but it was a shit show. You end up having _two_ servers instead of one: the actual backend server, and the server for your frontend. There was so much more complexity because we needed to figure out a bunch of craziness about where the code was actually being run.
Now it's dead simple. If it's PHP it's on the server. It's JS it's in the browser. Never needing to question that has been a huge boon for us.
Notice that nearly everyone pushing edge-execution JS has some infrastructure to sell you.
It's positioned as a ramp up for companies where frontend and backend devs work at loggerheads and the e-commerce / product teams need some escape hatch to build their own stateless backend functions
> If it's PHP it's on the server. It's JS it's in the browser. Never needing to question that has been a huge boon for us.
In what way has that been a boon? Context switching between languages, especially PHP, seems like an even bigger headache. Is it strlen($var) or var.length or mb_strlen($var)?
Do you ever output JavaScript from PHP?
My biggest question though is how do you avoid ever duplicating logic between js and PHP? Validation logic, especially,
but business logic leaks between the two, I've found. Doing it all in Next saves me from that particular problem.
why would anyone send JavaScript from the php? why care about duplicating a couple json translations and null checks... it's all code is today anyway.
and switching languages? you can't use most of js as it is. even something as simple as split() have so many weird bugs that everyone just code from a utils lib anyway.
spoken like someone who's not experienced enough to realize that duplicated code needs to be kept in sync, and then when it inevitably isn't, it'll lead to incidents, and also can't write JavaScript without using leftpad.
I am a backend dev, and I needed a website that was temporary for an event. I thought to myself this would be a good opportunity to learn some frontend development.
After looking through the 20 different popular front end frameworks and getting confused by SSR, CSR, etc. I decided to use Nuxt. I thought oh this is great, Vue makes a lot of sense to me and this seems like it makes it easer to make Vue apps. I could not have been more wrong. I integrated it with Supabase + Vercel and I had so many random issues I almost scrapped the entire thing to just build it with squarespace.
I dunno, I find the blur more visually distracting than a hard stop.
I would rather borders and color contrast to create visual separation anyway. That approach takes up less space. White space takes makes your UI less dense, but blur is even worse.
Either way… how does that relate to my keyboard being transparent? I don’t need to see a completely illegible blur of the colors behind my keyboard.
I just turned on the “reduce transparency” setting and it’s much better.
I don't know much about film industry, and I have a ton of brainfog from being sick today.
Could you say more? What made them a hotshot? They thought they were like, creative geniuses with digital film or something?
reply