So there are a number of people on this site who are not at that level and they get resentful that someone might get a deal like that rather than try to find a path to getting a deal like that for themselves. That's crab mentality and it helps no one.
The way to get there is to refuse to sign non-compete agreements unless they come with an equivalent clause to what I got. When you sell yourself short, you sell everyone else along with you.
I think Nim would really take off if there was a good and actively-maintained SDK for a major cloud provider, or even for one of the larger VPS sellers.
Thanks for making these, I actually had no idea these existed! I don't "need" them now but seeing these gives me ideas for projects and makes future things easier.
I wish discovery of community libraries was higher, I'm constantly discovering libraries that do amazing things 'hidden' away. I know there's https://nimble.directory/ and https://github.com/xflywind/awesome-nim but most of the time I end up using a search engine for something specific only if I think of it.
I have trouble going near CockroachDB because of its name. It's absolutely unjustifiable from an engineering perspective, but the effect (for me, at least) is real.
MongoDB because mongo is a derogartory word in my language. It is an abbreviation of Mongoloid, was (apparently) used to describe people with Down syndrome, thought I've never heard it used for that. It's more colloquially used to describe people who act wierd or something that are stupid or made in a wierd way.
Svelte, the javascript framework is also something I've kind of avoided so far due to its name. While it doesn't really mean anything in my native tongue as far as I know, it is a very plausible word/spelling and it kinda just sounds unappealing. I can't help but reading it like that either.
I always took that to be a reference to "it's so robust, it'll survive nuclear winter," which is pretty cool if true. The last database standing after all other species die off.
Fun fact: the supposed extreme hardiness of cockroaches is something of a myth, and in particular they are not fond of cold (hence their affinity for human domiciles!)
Developers are human too. I think it's entirely justified as an engineering decision - if they care so little about people who feel differently about their name, surely they'll have the same lack of consideration for people who want to e.g. use a slightly different API than what they expect.
Totally agree. I got over it and installed it and was stunned that it was as good as it was. Now it's installed on pretty much every machine I own. I recommend trying it!
Same here. I know naming things is hard but they went out of the way to make it extra terrible. Stick to letters and maybe numbers if you want the version in the name.
In that framing, it is often the case that US-led "capitalism-at-any-cost" over-indexes on scaling the magnitude of the vector while leaving the direction free to be influenced by other entities. The EU approach is to disregard the magnitude while keeping tighter bounds on the direction.
I'd like to think that bodes well for the UK, since we historically have trodden the middle ground between both camps - but I'm sure we'll find some way of fucking it up and gaining neither magnitude nor direction.
A lot of early cloud adopters were more "nimble" organisations who didn't have deep ties to MS enterprise agreements. We are now in the phase where those large enterprises have gotten over their early cloud experimentation phase and are migrating for real - which will result in a bit of an MS resurgence I expect.
There is zero chance that your career is going to be detailed by sticking withS technology at this point - it just might not be the most interesting.
Azure is an inferior platform to the alternatives on a technical level, but they make up for it with stronger enterprise relationship-building than AWS/GCP, and they do generally try to keep up with broad AWS capabilities of not the actual quality.
I think most people can thrive in the situation you describe (extreme hard work) as long as they also feel a sense of control. I am at my peak (in productivity and "feeling alive") when 100% of my work hours demand my focus because I have that much to do. When I have a quiet period I get miserable; I can find plenty of my own ideas to work on, but they often feel either futile or wasteful - that part is my own problem. Similarly though, when I have too much to do (ie when I know that working 100% still won't get it done) I become demotivated - after all, it seems that none of these tasks are important enough to get proper scheduling, so why bother sweating over them myself?
Second point: working full-on as you describe can apply to non-employment too. The drive towards working fewer hours (for the same standard of living) is just a direct response to growing wealth inequality and general unfairness in society, not a softening or growing laziness.
Been battling with this mindset shift myself. When I get annoyed with myself for delaying a task I try to remember the concept of "last responsible moment" from the Agile methodology books; after all I've never missed an important deadline so far, so clearly my effort-estimate calibration isn't far off.
