I met my (now) wife after a long relationship that'd ended somewhat messily. I made the conscious decision to go all-in on the new relationship because it could not possibly be what I wanted it to be if I didn't.
My wife and I were married about 5 months after meeting. My friends and family were worried that I was leaving myself vulnerable to being wiped out emotionally and financially if the marriage didn't work out. They were right, in a way. But sabotaging the relationship on order to stay safe seemed a far worse risk.
We're coming up on 18 years of marriage, so I'm glad I made that call. In an alternativee timeline where this relationship had failed, I'd like to think I'd still go all-in subsequently, but I can see how it would get harder and harder with each failed attempt.
The idea is that bringing on a wrong candidate will cause more damage than missing a right one.
There's definitely a balance to strike, some companies would rather bring on everyone and find out who sinks and who swims, others hate firing and will do virtually anything to avoid hiring someone who needs to be let go.
Most arguments I've had about this take on a totally different tone when you ask the person if they believe there is more to human consciousness than what is inside the brain. I.e, is there some spiritual element animating our consciousness.
Often, people say yes. Those people almost universally cannot be convinced that a machine is intelligent. But, if they agree the brain is an organ, its not hard to convince them that the functions of that organ can be simulated, like any other.
Why do people want to be a part of something successful?
Becuase its frustrating to put effort and energy into building something only to see it discarded or destroyed.
Yes on the big timeline we're all building castles in the sand but most of us would like to be able to stand back and look at it while its finished before the ocean washes it away.
Equating this with parenthood is short-sighted. I have no children and will not have children in the future (indeed, I have taken medical steps to make this so). Nonetheless, work is money. To the extent I care about what I'm working on, it's due to a preference to avoid working on objectively evil projects. (Even then, I'm not sure whether there's a difference between working at, say, Microsoft, versus working at a hedge fund -- in either case, you're really just working to build the wealth of billionaires, after all.)
For sure, at least for me I don't have children etc, but fulfilment comes from the things that i want to do and work on in whatever way is intreasting and exciting to me, it's going to be very difficult for that to match exactly with a job, so my best hope is that the work itself is enjoyable enough, pays what i need to do what i want and then fulfilment comes with the things i do outside of work.
If you work at Meta and the Metaverse fails, I personally would not care beyond the immediate impact on my job, the part I had to play amount thousands of people would be of so little importance that I am not really that invested in it, as long as the day to day was enjoyable for me, I liked playing in that world and then i had the projects in my own life that were all on me, i'd be good.
I completely agree react/angular/vue have a place and there are instances where they are essential, but too many programmers are reaching for them as the "only" way to build a web app.
And old, boring framework like rails or django can absolutely provide an adequate ux, especially for smaller projects.
There is still a need for straighforward crud apps modifying business data for internal users, and rewriting these apps in a js framework will introduce a lot of complexity that is simply not needed.
Dockerized applications can still reach services on the localhost, but you may want to take a look at docker compose so you get your application and backing systems in one place.
It makes your local development environment incredibly resilient.
Do you have an example how that would work? I unsuccessfully spent quite a while trying to get a docker container running rails to talk to a docker container running postgre. And I wanted to postgre container to persist to the host's disk so I could save state between runs. Maybe that wasn't the best way to do it though?
Some products dont fit well with a one call close and are centered around building long term relationships with your clients. This is especially true in b2b. Maybe you were trained too narrowly.
You can have your great “relationship with your clients.” You will see how illusory that is when a competitor appears with a 50% better value proposition. Oh, and SOMEONE has to ask for the order.
