junkilo
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.
https://web.archive.org/web/20230519170640/https://www.newyo...
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.
or the piles of humans feeding the internet, tech and social media 24x7
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.
the new company's revenue went from 7 figures+ a month to 0 because of the virus and they are rightly freaking out
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?
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.
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:
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.
how'd I do?
It only takes one person to set a price provided they honestly believe in they value... and that person can be you.
> (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.
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.
good reminder to back things up.
Jobs come and go, great work is always great work, but friends are what I remember most.
I've struggled with similar in my career (eng@uber) to a lesser degree and these are some of my findings:
- in terms of long-term survival; friendship, connection and investing in humans brings much more satisfaction than any technical part of my work and will outlast the business every time.
- when I'm arguing a solution or iteration that I've designed, the harder I hold onto that solution the tougher it is to sell.
- every time I instruct an engineer rather than let them figure something out on their own it seems to not go in my favor.
- the best designs and implementations [at scale] in engineering [sadly, for my ego] always seem to require multi-faceted perspectives (a team) to simulate adequately and vet impact (business+social+tech).
- promotion and progression in an organization is a subjective mess, all biased, and largely driven by non-technical markers namely social proof, liking and perception.
Love what PlayCanvas is doing. They seem committed to the community and their people.
There's a broader argument for and against "specialization" i.e. studying other disciplines yields perspective etc.
At any rate, I'll share the ways I'm solving it presently:
* reduce the number of disciplines required to be effective * confront human resource management problems * build funnels to save time or improve process
I suppose I'm advocating tackling fundamental leadership problems in an organization :/
If you have any advice or ideas you can share I'd surely love to hear them.