>> Web development takes the lion's share of computing people pay for which translates to the work people will do (we need money for survival)
This just isn't true. There are so many systems where the web component is just the tiny part of the iceberg you can see, but underneath some form of browser client there's a huge mountain of computer-based technology. Concepts like containerization and microservices are far bigger than the notion of current web development.
2-stroke exhaust and new tires... Maybe it's the association with memorable activities like visiting a motorcycle dealership with my dad as a kid, or a mowed lawn and warm summer rain? Meanwhile diesel exhaust makes me think of those cold, cold winter days, waiting for the car to warm up on an ice-cold vinyl seat...
Maybe the "we love ads" argument is gone, but I still see the "I've trained myself to ignore ads" line of reasoning, which is countered by dark patterns exploiting thousands of years of evolution against ignoring things like motion and bright colours. Plus I'm not sure how you "ignore" non-optional ads between what you want and where you're at...
You didn't seem to get much of a reaction, probably because of your recommendations to go with proven (read: old & boring) tech, but I appreciate it. Front-end churn is real and, coupled with rapidly evolving and ever-abstracting containerization approaches, staying on top of it is a full-time job, best done as an employee.
FWIW, I disagree with GP. I'm more productive in React than in SSR, and I'm much better at code design and architecture with it. React is pretty much old and boring by now.
The apparent difference in our situations is that you know React and everything that comes with it. It seems like that'd be a good choice for you.
I'm not proficient in any of the currently popular frontend architectures. Gaining that proficiency and moving a 10+ year old product to a SPA type architecture would be a massive investment. I enjoy learning new things and pushing things forward but I can't justify that investment when it comes to the frontend. Instead, I invest in other areas to move forward in.
Yeah same here. I did years of generating JS heavy frontends with PHP for Ajax apps. Once I learned to keep all data on the server and functionality on the client I’ve become so much more productive when slapping together an MVP with react (and any backend capable of spinning up a rest, though I prefer python or go at this time.)
If I may chime in here, I would humbly suggest that it is best done by whoever enjoys it.
Sometimes that might be your employee, and sometimes that might be you.
I guess it depends on where your passion lies, and what your objectives are?
I imagine that achieving one's financial ambitions in a relaxed and enjoyable work environment is great - irrespective of which part of the stack one enjoys tinkering with the most.
Sending via SES and WorkMail ALL of my emails are flagged as spam, including replies to the original sender and things as benign as accepting meeting requests. We use it primarily for inbound, so not as big a deal but definitely going to move soon.
I understand where you're coming from, but you don't have to pursue your absolute best in everything you do. It's fine to just "do" things casually. I think people would be much happier if they prioritized participation over mastery.
Yeah, you will soon burn yourself out if you try to do the best in everything. It's really a matter of choosing a few key place to focus your energy and put in extra effort there, but to make sure you leave enough to do other things in life.
>> 1-2 months is a more reasonable tiny project timeframe. It gives you enough time to build something with substance, and test the idea thoroughly.
This is a similar timeframe that Basecamp uses for internal initiatives. I've been pushing for us to switch from 2-week sprints to something closer to 6-week features. If you're building on existing product or a brand new one 1-2 weeks is just not enough time for meaningful progress.
To be fair, there's only a few highways in BC and if you're going in one general direction, It's all one big road that kind of connects. We've got few very long roads that stretch out north and east from the coast, that work their way around the communities of BC.
BC's highways and roads remind me of tree roots all leading from Vancouver or the border.
This just isn't true. There are so many systems where the web component is just the tiny part of the iceberg you can see, but underneath some form of browser client there's a huge mountain of computer-based technology. Concepts like containerization and microservices are far bigger than the notion of current web development.