prea

> What's even the point of posting a photo of your child, with the face hidden? Seems very niche.

Might be a cultural US thing, but this is something my wife does a lot and I see a lot of people doing. It's one of those things that might not make sense if you don't have kids.

> All of the virtual ink in this article, and honestly most of the complexity in the field overall... and it seems to really all just boil down to, 'I think this looks cooler.'

IMO there's significant complexity in building a feature-rich frontend client. The "thicker" the client, the worse it gets. There's definitely a lot of 'I think this looks cooler' going around, but also we shouldn't forget that the need to come up with something better is partially a response to very real, very-not-imagined, frontend complexity.

I worked in React for a few years, although not enough to ever feel like I was an expert. This article resonated with me because I also got off the bus because of React hooks.

I've been using Lit.js for about a year now and something about it just clicks. I just wish it were more mainstream.

Am I missing something? What's the point of the tweet other than to elicit a reaction? And then in the replies: 'I CAN'T BELIEVE I ELICITED A REACTION!.

At every company I've worked at where I stayed for a bit, I eventually had to work on languages and stacks that I wasn't technically hired for/had interest in. At the very beginning I found this very hard, also wanting to quit/actually quitting. I've come to accept that this is actually pretty normal. The benefits to my career from working on a bunch of different stuff I didn't pick have been substantial.

Caveat: I probably wouldn't take the switcharoo at the very beginning either...if I'm told I'll work on A but actually get B, this is likely a sign of some important things not working well at the org.

We're not so different in age, and I'd be lying if I said I never feel the way you describe. However, these are some things that helped me, in increasing order of importance:

- Health. Covered already, but I'd add that you don't need to be in marathon shape. Just hit the basics: sleep, exercise (walking is enough!), diet. It's easy to feel things are ok in any of these dimensions but actually be out of whack.

- Do things with your hands. Humans develop insofar was they learn to manipulate the physical environment around them. This is one of the tenets of the Montessori pedagogy, but I found that it doesn't just apply to kids! I feel _great_ when I install a toilet, paint my living room, fix the car. There's just something about physically doing stuff with your hands.

- This one is hard to describe...I took inventory of my 'philosophical operating system' and realized that I was organizing my life around something without legs. In my 20's I was heavily influenced by stuff like '4-hour-workweek' (lol), the gary-vees, the pg essays, etc. It's not jut practical advice...it's a philosophical system and worldview. When I looked under the hood, it was all spaghetti code. It couldn't stand up to more cogent and complete philosophies, which I found literally down the street.

It's true that there are many more choices to make for a JS SPA compared to RoR but isn't this just a fixed cost? Pick once and then stick to it. Use the same things for your next project. Done.

I'd venture to guess that for a RoR newbie, it takes just as much time to understand the 'glue' (I've heard people refer to it as 'magic') that makes it all work together behind the scenes.

This sounds very promising! I used to create checklists in Confluence and that was pretty hard to manage.

One question - does this only work for public releases or will it also help me with internal distribution (e.g. ad hoc/testflight for iOS)?