Some countries don't have cents, some countries have 3 digits of cents. So, yes you can but you also then get thinking you can express everything as ints. But, the moment you need to convert from KWD to VND (84000.00:1) you could be at the edge of the size of a 64 bit int. Note: VND is pretty stable, when currencies start deflating the numbers can get crazy.
A decent way to cram for an exam you don't care much about is to hand copy the course material too. You'll most likely end up retaining enough to pass.
Many fintechs are not licensed to hold funds and work with bank partners who hold your actual funds. That allows them to say they're insured because they're not co-mingled with the corporate funds in the event of insolvency. This doesn't stop them from making accounting errors.
Best advice -- find a local running club that does track workouts. The group dynamics will be incredibly helpful as a baseline. Sprinting is big on strength low on endurance, that's why you see muscular sprinters and lean 5k+ runners.
IMHO the biggest factor at being fast is training fast and understanding this is a multi-year effort not a quick fix. Odds are you will need to change slightly your foot strike pattern, this is a long term project, not something that's done in a month.
Keep in mind that the layoffs earlier this year have still had a huge impact on the job market for software engineers. Many companies moved their hiring bar higher and have gotten more selective over their canidates. 2 years ago, if you pretty much had a pulse you could have jumped fields (yes, some jobs did require specialized knowledge).
Many Canadian companies are not doing "interesting" things so I can understand the perspective of being at the long end of the funnel on sprint tasks for a product that might not be getting huge marketing wins. You've already taken the first step at figuring out what's interesting to you. As others have said, start learning about some topic areas find the meetups over those topics and start networking and getting to know people in the field.
> Keep in mind that the layoffs earlier this year have still had a huge impact on the job market for software engineers.
People keep saying this like it's a fact but I've not seen anything in the employment data to suggest this is remotely the case. Tech unemployment is startlingly low, and even during some of the massive layoff months, tech was still adding jobs faster than it was shedding them. Last I checked, tech unemployment was at 1.5-2%, much lower than the national average (USA at least).
I think what I’ve seen is that with the near hiring freeze at Amazon and a substantial slowdown at Google means that the next tier down of employers are having their pick of candidates that they might have had a harder time landing when Amazon and Google were hiring 5-figures of SWEs every year. So, even if everyone ends up being employed, the selectivity could still be higher than normal. I know we amped up our thresholds for hiring quality.
My anecdote having just switched jobs is that It did not take long to get a new job, only about one week to get an interview, a month to complete the process and start and I had 2 offers. However I applied a bunch of places, and even with referrals, only a small fraction got back to me which 3 years ago when I last changed jobs almost everyone always did.
I cannot empasis how true this is. The classic UNIX problem was that the LPT printer daemon has an issue (it had lots and lots). But, none of your systems were running LPT, but you still had to patch 1000+s of systems just to maintain a security policy.
What's different between full on UNIX systems and Docker, the possibility of deploying code based on scratch images. Imagine a system which only had the pieces necessary to run in production, your security exception reports would go to zero.
It’s almost free to rebuild and redeploy from a Dockerfile if you have a good devops culture. This would replace the traditional unattended upgrader with scheduled reboots.
Was excited to see a non-GC'ed search engine that looked solid. But, without having the replicated - distributed version of it in the "free" tier makes it hard to really evaluate.
Touching on the writing point. Think of it as muscle memory, if you watch people put together PowerPoint slides you see that those who do it regularly can create a solid presentation quickly. As a developer, at some point you're going to be writing some basic technical specifications to decompose a project. Even if you've been only writing to yourself, having the ability to quickly pull together a document that communicates with others is an asset.
