308 karma · joined September 18, 2022
Signaling you are sick and working via a status message just seems like an odd choice. The pessimist in me looks at this as signaling for sympathy.
The gov't (re: JT) pushed this through to some fanfare but has resulted in oversupply and fairly botched execution as some other posters have mentioned already. I'd expect to see contraction in the suppliers / M&A as some of the growers and distributors start to go belly up.
On the other hand, Facebook is much more likely to err on the side of India given the much larger population and associated $ potential and THE BILL.
Canada is not exactly an espionage expert relative to places like India so I find it highly unlikely that we (Canada) will be able to figure this out in the short term without external help.
I recently sold my downtown Toronto condo (principle residence) after 8 years and the returns are arguably higher than the wage I've made over the same period of time after taxes (I work at one of the big 4 consulting firms, so a fairly average salary for the city).
We are now with our backs to a wall where we cannot let house prices drop, which means we cannot increase supply to quickly or risk a good chunk of the population losing a significant portion of their future buying power....that is unless wages shift.
Vanilla sex work was disrupted by porn, porn by digital distribution of amateur content/gig industry (pornhub, onlyfans etc.), and now the gig work by AI-enabled 'companionship' as they put it.
Insta has more than enough content that is very similar to what these ads are showing (both male and female), so I'm not entirely sure whether it's a "double standard".
People crave change has been my main lesson learned.
This is less endemic on the securities and wealth side. Business and retail banking back-end transactions and processing have extremely large COBOL/mainframe dependencies. The systems have been built over decades. Some of these banks have tried to transition to newer tech and progress is very slow + bumpy. I'm not a cobol dev but from what I understand it is spaghetti'd to hell and back.
There is def a labor shortage but more of the younger gen is being exposed to this tech via the transition/transformation projects. But def. a dying breed from what I've experienced.
note: except for the healthcare side, all this experience is OUTSIDE the US
- Most of what you see from the outside is not the whole story. SBF or the other companies with no clear mission getting $, well...We seldom know the whole story including how much of the $ is actually theirs and how much is owed. Dont anchor yourself on others.
- It is highly unlikely that you are unemployable, try going for industries/markets/positions that you haven't gone for in the past because of your own opinions. (I reluctantly went into an industry I held back from for a long time only to realize it was foolish of me not to be open minded)
- Show/display/market to your prospective employers what they want to see/what role they are trying to fill. Just because you have experiences doesn't mean you have to lay it all out..just enough to show that you fit the role they are looking for
- Fundraising is difficult especially if you have a personality that is not conducive to networking. Try alternatives...gov't grants, kickstarters, etc.
At the end of the day I don't think there is any secret sauce other than hard work, patience, and a handful of luck.
Keep trying and hang in there :)
Having people who trust you and are willing to help you out is a far more potent than having 'X technical skill'. This doesn't necessarily mean going out of your way for 'networking events' or espousing your great and wonderful skills to everyone you meet. It can just mean staying in touch with the people you have enjoyed working with/for.
Keeping your skills is still important, and if you're a curious person you'll probably be doing this anyway. But there are a lot of us curious ppl out there...on the other hand, your network will be unique to you.
The closest thing to a FU skill though is probably COBOL...
But a bad management style would still trump this.
I'll share some less technical thoughts that I think hold true regardless of the approach taken (rewrite or not).
My experience with changes like this is that you need to be as transparent as possible to both parties (the devs, and your execs). This means consistent comms around goals, achievements, and crucially the challenges preventing the first two.
With any team, you are not going to win much by implying that their work sucks or the thing they have built is broken. While they might know it, a third party is just not going to get a good reception with that mentality. It will be important for the devs to understand why the change is needed from a business perspective (e.g. time to market is too slow to remain competitive, changing regs, etc.). The intent here is to focus the devs on what the hope is for the future as opposed to shitting over the thing they have poured their blood, sweat, and tears into.
With the execs, they need to understand just how bad of a shape things are in so they give you and the team the space they need to make a significant enough change that isn't just going to revert to the same mess as before. If you're dealing with tech background execs it might be a bit of a simpler set of convos. But if not, then you are going to have to illustrate for them how bad things are. One way I've done this is to first get an idea of what the execs want as the final state of the team / codebase / product (e.g. time to market is < 4 wks) and then draw them a picture/flowchart of what it takes to get that thing done in the current state. Could use some form of value stream map to do this as it combines players, states, activities, and also timelines.