So cool!
152 karma · joined February 21, 2018
---
Sorry, but we’re having trouble signing you in.
AADSTS500200: User account <my email> is a personal Microsoft account. Personal Microsoft accounts are not supported for this application unless explicitly invited to an organization. Try signing out and signing back in with an organizational account.
Before anyone say it, coding interviews are stupid, but having a proper job (at a proper company, with proper career paths) is not.
For other concepts, like you said, Python helps you focus on the concepts themselves better
Each char can be an a or b, then repeat, not "a repeating seq of either a or b only"
(a|b)* = X* = x1x2x3... where each xi can be "a" or "b"
I was mid-senior when I changed to a research SWE job. Might be able to offer some insight on some specific problems.
But in general, each place has its own expectation about code quality and process. One of the most important skill for a SWE is to not expect anything when joining a new place, but adapt to that place's way of working instead.
What is this dichchankinh.com domain?
At first, only a few talented people can do this. Then as the tools they develop get better, the job will be more accessible.
The Hypothesis library for Python has a pretty good docs explaining property-based testing and how to use it.
Finding niche areas such as Rust, Haskell, Clojure, Elixir, Julia, C/C++ would maximize your chances because the mainstream language jobs will be swarmed with formally educated candidates.
Node.js was THE first back-end JS thing, and its "micro" philosophy kind of set the precedent for everything else that follow in that space. It was the time when people started to feel Django/Rails are cumbersome for some of their needs, too, so the MVC approach never caught on for JS devs.
So I think it's just popularity. Pick whatever tool you deem suitable!
Don't shoot yourself in the foot. The moment you let job#1's managers know about job#2, you will only have a part-time job left