Not that I disagree with them, but their forecast is based on never believing it would work in the first place. All their reasons for it continuing to fall are reasons it should not have reached its ridiculous, frenzied peak.
> Our view that cryptocurrencies would not retain value in their current incarnation remains intact and, in fact, has been borne out much sooner than we expected
Thanks guy; really went on a limb there with 80% of the world hesitating to jump into bitcoin because they thought it was a bubble. Very newsworthy opinion you have there. I'm glad you admit you had no idea on the timeline either. That was generous.
Author says don't follow a morning routine, but then mentions they have a morning routine (breakfast/trainer).
Author says don't focus on the morning being your peak time, you should find the time of the day that is the peak time for yourself. Ignore the fact that their good breakfast and work out helps power their peak times. Inconsequential.
Okay, but that's why those morning routines have you do the rote/everyday stuff quickly in a short window, so you can have longer peak times during the day. Notice in their long list of things blogger says you should do is none of the real work you get paid to do.
Granted, you don't have to wake up at 6am; but if you're going to have a routine that you do every day, that you should optimize such that it doesn't get interrupted by work messages and e-mails or other responsibilities, when's it going to be?
It's going to be early in the morning.
The author is making the exact point they're attempting to refute. You should have a morning routine, it should be filled with things that are good for you and harder to schedule during the day, you should optimize the specifics to what makes you feel good, and doing it will make you more productive as a result. Great.
I'm glad the author took the time out of their day to correct all those other incorrect bloggers who didn't know what they were talking about.
All these defenses are laughable when put in any other context. Try answering "why black people don't code" with a straight face and ignoring systematic disadvantages. I have not seen it down without exposing a bigot.
I've seen the "each group has its reasons" fluff as well, but those defenders are happily living in a world where only one type of group makes good programmers. Out of a whole world of groups, only this type of person can write code.
The narrative that this lecturer understands all disadvantaged groups because he's from one himself is a false narrative. Using that to build credibility for his arguments is laughable journalism.
They're going to have tangential skills to the new platform.
Get your network team to learn all about VPCs and networks and security groups and peering and VPNs, train them to be your in-house experts to deal with changes and expansions and to help trouble-shoot issues.
Chances are you're still going to have systems, your systems engineers can be repurposed to better tie in your monitoring tools, your security tools, etc. You're going to need authentication and identity management, and probably have internal people handling it.
If they're motivated to keep their jobs, all it should cost you is a $5-20K/head in training.
That's peanuts compared to the turmoil of everyone thinking they're going to lose their jobs, or the costs of hiring new people w/ pre-existing cloud skills. It is cheaper than the stop-gap of paying outside consultants till you can bring in the interior staff. Also, these people _know_ your existing systems. They know your business logic, they know what needs to be up and they know what can't break on Thanksgiving weekend. That is valuable knowledge that is a hidden cost in rehiring the work force.
You're going to find new challenges in the new system. If your employees are willing to transition, then transition them. It is your best bet.
If you have a subset of employees that can't/refuse to transition, put them on performance improvement plans. No rumor mill - if you're on a PiP you need to shape up or get out; if you're not on a PiP keep doing well, your job is safe.
The "non-profit" group is a scam, where the operator of the group gets paid very well from the operating expenses of the non-profit.
An event like this would be leveraged to draw attention to the cause, thereby the group, thereby raising more funding to spend on further self-gaining operational expenses.
As someone who missed out on Bitcoin, these stories make me feel better about myself. Probably self-deluding myself into missing out on more opportunity, but there is a clear wild Wild West feel in these messages.
Covering up bad code and bugs by yelling hacker Wolf. Either way that doesn’t absolve the banker. If your bank is robbed they still owe you that money. That’s the deal. They insure against that. But what is a financial institution in the crypto world is telling customers that they can’t pull out their direct deposits because they left an ATM unlocked.
People would riot in the streets if that happened with BoA.
Worse is the begging in reddit comments for everyone to HOLD their nano. It’s begging for regulation.
It is theft. It's not a scheme, or a game, or a trick. They are stealing money. It needs to be made punishable.
As these frauds get more sophisticated, it won't just be "dumb" money getting burnt. The answer to "someone stole this from me" isn't "well you shouldn't have been so dumb" - whether it is your wallet, a package from your doorstep, or a bit. Theft is theft.
For your Boss, replacing you will take much longer than the 6 week sabbatical she's giving you, AND it will probably cost her more than your salary in that interim. So if you're quitting today, she'd like to take the gamble that you stay. Her gamble is that you are actually happy at your gig as you say you are, and she can save herself a whole lot of hassle. Worst case scenario she loses a month of lead time on an at-least-3-months headhunt. A bit of a wincer, but you can try to make that easier by letting her know as soon as you know that you're done.
If the job market was different, then I would be much more timid about the open strategy. If you do, in fact, dislike your job and are never going to come back, then you're changing the odds on the gamble and hurting your Boss unnecessarily. This could all backfire if your Boss doesn't value you as much as you think they do, but no one is usually off-base on that.
Been burnt out myself. Coached a few friends and coworkers through their burnouts. My advice: See what's the longest vacation you can take.
If you're at the point of quitting - just be honest. Tell your Boss that you're burning out and thinking of quitting. You would like to just take a month off or six weeks to recover. You can phrase it as something else entirely to a different part of the team, but be honest with your boss and see if you can get approval for the time off (even unpaid) so you don't spend your time off worrying about finding a job when you get back.
Then take it, worry free. Don't make any decisions in the first 10 days. If you manage to make it 7 days without touching work things, then start thinking about it. Think about whether you liked what you were doing, whether you want to go back.
I've found this strategy has worked for the handful of people who have tried it.
https://www.packet.com/about/compare/google/