Tech’s strangest job listings: Straight from the “daily workplace automation destruction” protocol.com reports the future of job descriptions, as indicated by job postings today.
Glimpsing the future in eye-opening tech job listings.
The article found quite a few interesting job profiles that companies apparently look for today already:
Product Management Predictions: With January already over, it’s a bit late for annual forecasts. But then again, looking into the future is a secret superpower every Product Manager should look to develop. Therefore, it’s never too late to have an understanding of what comes up next. Mason Adair of Digital Product People did so for the profession itself.
Ten Wild Predictions, One True Story and some Solid Career Advice
From the article
Just like the industry is changing. And the article makes an effort to put into relation the different aspects Product Management has. Mason starts his thoughts by looking into public available metrics that indicate the importance and projected relevance related to management of products. In this analysis, related topics range from Agile, Minimum Viable Product, Design Thinking, Lean Startup, Product Market Fit, Rice Prioritisation and Net Promoter Score all the way to Jira, Trello and Asana. With an analysis of how relevance for these topics changed over time, the article goes into setting the scenes for professional trends that influenced the past years. These include economic environment, the introduction of new technology, a demographic shift, increasing societal fragmentation and climatic change.
Product Management Predictions shape the conclusion in his article: 10 wild predictions I believe are not that wild. The top most prediction, Product arriving at the C-Level, is almost no prediction anymore. Digital companies already have recognised the importance to actively influence direction towards customers.
The Y2038 problem is similar to the Y2K problem. We’re exactly in between both about now. Both are 18 years away, in either direction. While Y2K is over and was obvious to everyone, Y2038 is not.
The issue here relates to a representation of date and time in Unix systems, and is therefore sometimes referred to as Unix Y2K. The root is the convention to store date and time information as 32bit unsigned integer in such systems. This means, possible values are limited. Time-differences in seconds, starting from 01.Jan 1970 cannot span beyond 03:14:07 UTC on 19 January 2038.
Calendar
The Y2038 problem will make all calculations beyond this date impossible, until migrated to another representation. At the time being, this seems far away. However, the problem casts its shadows already. Industries, in particular financial markets, often rely on long term forecasts.
Governance issued treasury bonds come with with the longest maturity. Often twenty years, sometimes thirty years. Calculations for complex, long running financing models easily try to estimate returns 20 years and beyond into the future. This is already beyond the problematic date that Y2038 brings. The code to run these calculations is typically complex and stable. Sometimes, it is as old as from 1970. Back then, this date-representation Unix engineers introduced this approach. 32bit covered a long period. John Femellia has a thread, over at Twitter, telling a story about the upcoming issues today.
⏲️ As of today, we have about eighteen years to go until the Y2038 problem occurs.
But the Y2038 problem will be giving us headaches long, long before 2038 arrives.
Natürlich ist es immer schwierig, Vorhersagen zu treffen. Nachdem es sich bei dem Urheber des Zitates um einen führenden Ökonomen handelt, kann man das ein bisschen strenger betrachten. Um etwas positiver zu sein, kann man an der stelle vielleicht noch anführend, dass Deutschland offenbar nach wie vor Marktführend in der Anwendung von Faxgeräten ist:
