This is a great question, and useful to many others as well!
In my experience (25+ years), the first step is to realize what your main objective is if you had the big picture in your head. Then you can apply what you want to learn and work backward from there. Effective integration work might be best served by focusing on software contracts. Performance improvements might force you to think about which parts are better or worse than the required capabilities.
I sometimes take on bug fixes, UAT to force myself down paths which I would normally not encounter. This helps me dive in deeper to new areas as well as avoid those that aren’t my cup o’ tea.
I used to be able to keep a lot in my head, now I prefer only to keep the index in my head, but do the actual look updirectly in code. :-)
Quite frankly, it’s hard to recommend any Cloud Service nowadays. Technical issues apart, the strategy _everywhere_ is to maximize picking the customers’ pockets. AWS is super expensive, Azure is super unreliable and GCP … well, it’s reliable yet features on it could vanish at a moments notice.
Tried it, alas, without success -Two big factors:
1. the infrastructure that made this possible in the 90s isn’t there anymore (at least in my part of the world).
2. The surrounding world requires information exchange at physical boundaries. These too have now been “digitized”.
The article focuses on Productivity as a sole cause for employers insisting on RTO. Yet, In some cases, we have CEOs on video record stating how remote work options help them hire and retain top talent.
I feel there are other factors such as government tax write offs/subsidies related to RTOs - eg employees cause retail around offices to have lowered traffic… hence lower sales tax revenues.
Why won’t employers just come out and say it? Your guess is as good as mine.
Well, yes and no. The wealthy have not experienced a hard landing, and at the same time, the wealth inequality has never been greater. An entire generation now has no prospects of buying a house, even renting is hard, etc.
Truly a sad event. I never met him but found his work to be so well explained, even in writing and practice. Wrote him an email once and got an informative and kind response. Highly recommend folks to read his website to get to know how to write well and convey complexity in detail, as a story.
Yup, I often speculate that for me, perhaps for many others, apps (and the Android/iOS platforms) are the source.
I’ve been slowly switching to web/desktop based alternatives- those too have their issues (eg correlating all the traffic out of my single home NAT’d IP address.
Mulling deleting apps off my phone as well, but many non-app “mobile” experiences are completely unusable.
Same here. I know that a fair bit of the data they have on me is inaccurate. Yet, to delete that, along with accurate data, I’m being asked to enrich their data with even more accurate data. It feels like the old “click here to unsubscribe” scam that actually just confirms a real person behind an email.
I would love to know who sold them my data though. That would allow me to stop the flow more effectively before I felt okay deleting at the terminal data broker.
In my experience (25+ years), the first step is to realize what your main objective is if you had the big picture in your head. Then you can apply what you want to learn and work backward from there. Effective integration work might be best served by focusing on software contracts. Performance improvements might force you to think about which parts are better or worse than the required capabilities.
I sometimes take on bug fixes, UAT to force myself down paths which I would normally not encounter. This helps me dive in deeper to new areas as well as avoid those that aren’t my cup o’ tea.
I used to be able to keep a lot in my head, now I prefer only to keep the index in my head, but do the actual look updirectly in code. :-)