if you know you know: thinkpads do make for happy compute.
fwiw, thinkpad/lenovo isn't the only team* can assemble a pc properly. its just that they tend to keep working even after you drop them and spill coffee on them and come with an escape key. <.<
*] it's really the sub-culture/team behind thinkpads that we appreciate, which ironically isn't normally distributed throughout all of Lenovo.
*NIX is the only viable choice for mission-critical desktop stability in 2023. But that isn't to say Windows isn't feature complete. It is still king when it comes to gaming.
Desktop stability and reliability hasn't been a top-level OKR at Microsoft for many years. The company has been growing more product driven for years and falling victim to roadmaps being driven by muggles.
The only place where you can actually design a truly stable and reliable desktop is with open-source kernels and user software.
I have less problems with stereotyping than with the hum of a million managers patronizing remarks, like this article from PG.
I've grown accustomed to negs' (microaggressions) like these, but they do a greater injustice to actual genius. Mutual respect in a team will never be achieved when people treat others in this manner.
we ran the numbers continually and like others mentioned, it was a no-brainer to build on-prem. that said, there are a few use cases where aws/gcp are a great fit. people selling cloud without putting in real engineering work to enterprises generally make my life harder than it already is.
my new company just withdrew their offer (I started in a couple weeks) and I just left my previous gig (AV startup). backend+infra full stack python/go stuff
the new company's revenue went from 7 figures+ a month to 0 because of the virus and they are rightly freaking out
> "I had to say yes" and "I had convinced so many talented people to participate" and "How could I let their magnificent work go to waste?" and " and "I wanted him to see me as an artist [not only as a prop for sex appeal]"
as a Dad with daughters I am horrified by this evil. Coercion and oppression to obtain debasing sexual content makes me sick: "There was no room for negotiation. I had to say yes."
Why do people go to such great lengths, even to compromise their personal ethics, to please others peoples imagined sensibilities or expectations?
Contracts are for when a relationship breaks down, not the other way around. The "contracts" offer protections to parents offering a legal path for enforcing access to their children as well as financial protections.
It also seems to offer access to additional social and cultural collateral than just cohabitation and has several inferred expectations in various social spheres.
Parties in a relationship sometimes have wildly different experiences, expectations and motivations "in love" and marriage provides a way to reduce this complexity.
There aren't many things that test your will and resolve more than having to sign a big contract on something. What people will commit to verbally is often vastly different to what they will actually sign to when it's in writing.
Having used both from the prototyping stage to very large scale my answer: It doesn't matter.
They are both plenty feature complete to work well for relational data type problems. Grab the one you have more exposure to and you'll be fine.
That said, I'm still using mysql-innodb (latest percona) because the built-in replication has had more time to bake and its concurrency model (think 100k qps+) is plain better. For further reading see:
1) Learn one thing really well and stick with it until you master it. Human confidence isn't wired to derive satisfaction from breadth of skills. The stronger single skills you develop, the easier it becomes to develop context and understanding as you add to your skillset.
2) Get solid on the basics and stay current: data structures, algorithms, computation and basic operating systems. Without these you'll never reach high levels of competency.
3) Develop boundaries. I've seen stellar developers reduced to a pile of depression and anxiety by poorly trained managers getting them to overcommit. Learn to know what you know well and what you do not know well. Push the rest back onto your manager and make them do their job.
4) Take time to enjoy and savor this time. We're in an age of technology that has never before existed.
Story:
As an engineer that enjoys fashion but has limited time for the hobby I would like an app that can help me self-evaluate fashion choices and arrangements so that I can have more fun and look better.
> (devops guy) hi, im here for the lead devops role
> (CTO) awesome, you'd be a great fit here. can you write a sudoku solver in ruby real quick?
> (devops guy) [writes solver in ruby]
> (CTO) wow looks great... when can you start? do you have any questions for me?
> (devops guy) I do have a question: how do you shard your bigdata installations and what is it built on?
> (CTO) oh I wrote my own, we call it redisbigtable -- its the worlds first CAP compliant data store. oh, and we shard by customer.
> (devops guy) thank you for your time.
You have to store data on the client endpoints in realtime logistics applications; its just how it's done.
If you don't, networking failure scenarios will destroy your user experience since you'll end up with frequent irreconcilable data gaps with cellular networking being what it is.
tags + notebooks + cross platform + rich text + search + clipping + images + shortcuts. I don't know of a offering that rivals it. Google keep is for kids, not for real work.
fwiw, thinkpad/lenovo isn't the only team* can assemble a pc properly. its just that they tend to keep working even after you drop them and spill coffee on them and come with an escape key. <.<
*] it's really the sub-culture/team behind thinkpads that we appreciate, which ironically isn't normally distributed throughout all of Lenovo.