1,403 karma · joined March 4, 2014
Feel free to email me if you ever want to hang out in the Boston area or talk futurism, philosophy and technology.
Very few people are going to bother writing apps for another ecosystem. Also, more apps means less control by Amazon which won't fly
Sure, the tobacco industry is "right" from the angle of their personal riches to push something that has cost millions of lives and fight government resistance. Same for oil companies, plastics, some parts of pharma, etc.
From the reference frame of society, which the government represents (ideally), they are in the wrong to sell put millions of people for their own gains and what you'd want a representative government to do is help society's interests and adjust as the world evolves.
In this case, the reason for making people spend hours of their lives, untold amounts of stress and billions of dollars is so some people can: 1. Make money, and 2. Fulfill a personal political philosophy
Maybe it's okay if governments tip the scales in favor of the masses here...
2. Start a consultancy company and overcharge clients to do this work.
3. Realize that many companies will not reward you for your efforts as you expect and go back to 1
If a group has repeatedly shown that they will use their tools and power to oppress others, why give them tools that increase their odds of doing so?
You have can the same batteries (or engines) in a car and get widely different driving dynamics. How does it put power down to the wheels?
EVs are fantastic 0-60 machines in a straight line but the luxury brands you listed care about more than that (including status, of course). How does it corner? What happens when I floor the accelerator at 70mph? Does the car feel like a wild animal you're taming or a machine that feels like an extension of your body?
Then you get to the other differentiators of interior design, extra tech capability, NVH management, etc. I'm excited for those areas to see some more useful innovation once 0-60 times stop being interesting.
I think vehicles like the Prius, Leaf, etc are for the same audience as the corolla, altima, etc buyer. The playground for those who care about a particular 10% of their driving/badge experience will always exist regardless of what powers the vehicle
There's a setting for that. Settings > Share Screen > Window size when screen sharing > Maintain current size
I'm sure you can imagine why this isn't the default. Many people work off their laptop screens and low res monitors. Few have 32" 4K ultrawide magic beans ones so full screen helps them actually see the content.
> - When the call ends, just end. Don't show me anything more with zoom, or make my screen go to a zoom/call ended modal.
I wonder if this is so that people don't panic, wondering whether the call _really_ ended or the window just disappeared by the other person can hear them.
> I find myself becoming my worst self on here, whether I want to or not, in reaction to others being their worst selves too. It's difficult to rise above the fray.
You always have a choice. If you display your worst self on here, you choose to do so. You can opt not to engage with comments that are a negative to the community.
I'd be curious about how success is defined here. Career is a pretty narrow lens to define it by so I'd hope for something more expansive.
Many of the benefits of having friends in high places are outside of traditional career ladder. The expedited (insert annoying process here), the vacation you're invited on, the unintentional influence you have on some big thing because you happen to be an ear to the decider, etc etc.
At some point, they decided that an IC career ladder was important and instituted it. Management always had a ladder so that's not new.
What changed?
So, a solo dev cannot, in fact, pull this off.
If you do job x and your employer pays someone 20%-50% more to do the same job, what are your options?
AI increasing the music in the world and lowering the bar to creation will mean it can both generate music specific to a few people's tastes and guaranteed top 100 hits in some regions. Much like many human artists can do today.
I'd expect the interviewer to engage and set some helpful boundaries (and the interviewee if they have the experience to talk about what changes between the two situations)
Your trivia knowledge is great to impress like minded people but irrelevant if the problem space doesn't depend on it.
PS: Someone could consider you a pretty junior engineer if you ship: "if(!!1 && b.some(e=>e>6)){
foo();
}"
because the you're increasing the risk of error in a codebase that would likely be maintained by people of varying skills. You write code to solve problems and you write code so regular earth humans can grok it and manipulate it to solve problems.
Writing code with a high risk of introducing problems and misunderstanding does not signal senior in many domains.
This is an interesting one. If you're talking about software engineering, I hope you interview questions check for that.
Many people memorize by rote, "build x system, make it FAANG scale" and our industry rewards that. Many small and medium companies have delusions of grandeur that they need solutions Meta and Google do because obviously, they will be the next Google with enough time. Things get overengineered and pragmatic choices are discouraged.
Promotions become about building complex systems/services and the goalposts keep changing.
I hope your group is able to both hire for and promote the kind of culture you need for your domain.
> and my team's velocity is badly bogged down by some tech debt, then the right allocation to fixing it is 100% (fix the shit so we can go fast forever.)
That's impossible. Software, like all things in nature, evolves and degrades over time and there is unlikely a magic 100% fix. Something can always be improved.
> On the other hand, if some "tech debt" doesn't actually impact team velocity/clients (eg, some code is "bad" but it's in a part of the system that's never touched) the right allocation is 0%.
Tech debt is also a great way to get your executing development team down to 0%. Yes, some people leave organizations because the code quality is bad and no one cares to improve it and it makes everything just a tad worse. This can compound over time. One day, the thing that is never touched will need to be touched and no one will be able to understand it in a timely manner, leading to other failures and re-prioritization.
> The X% approach seems to happen when engineering and product fail to have that conversation, fail to understand each other, so they have to just get a flat allocation each.
Agreed, a constant conversation is a good starting point but eventually, there will always be a bias in one direction. As you demonstrated, your bias is "There's ultimately the only thing that matters - getting value out to the customers". This makes you more likely over time to prioritize shipping to the customer over invisible improvements. The feedback loop continues until things breakdown. If you're in doubt, go ask your EM/TL partners if there isn't some technical debt they think is more important to address in the next 3 months than whatever you're currently trying to ship.
Technology organizations are quite complex systems but i appreciate your attempt at simplifying.
> microwaves
Many cheap motels do not in fact have microwaves. Buying one for $15 is great if you live in a place where people are selling working microwaves for that price and eveyrone else is not also poor and looking for a microwave.
> They took the time, why can't everyone else.
Not if you're working 3 jobs and barely have time to sleep while being a caregiver. Some people don't get to take time off to do things.
> There are no such thing as food deserts. I've seen the maps, and yes, there are areas that don't have large grocery stores.
Perhaps talk to someone who'se lived in one? There's quite a lot of arrogance to say "I've looked at the maps so your problem doesn't exist" from wherever you're based on earth.
There are solutions in many situations but the cycle is vicious and you're one bad step away from getting eating alive in many places. Poor nutrition -> health problems -> limited time -> getting laid off for underperformance (or plain cruelty). It isn't always a way out in life without a dollop of luck.
1. Usually, policies around max % pay raises are set the organization level. In the name of equity, the right battle to fight is having a higher cap for everyone which a middle manager is ill-equipped to do well.
2. Yearly budgets are set early partly based in the above formula, you'll need to be in a room with the C-suite to make the case that costs should be higher than they are next year to right-size everyone.
3. Sometimes, you requests for outsized adjustments get rejected. "Hey we're paying Senior XYZ less than New Hire XYZ, can we increase Senior XYZ's comp by 20% to match the market rate?". Some answers: A. "No, it's against policy and needs an excalation. Sr XYZ isn't critical enough to the business to change the rules. B. "Sure, but you still have $ABC budget for the year. That raise will mean reduced budget for person G's promotion or we give up headcount next year and Project U is at risk, etc etc".
I'm sure others here can add even more examples.
I've come to the conclusion that any policy that is not "We will automatically raise you to top of market"* like Netflix will have this problem.
For the C-Suite, that means costs are a bit harder to predict and it also means that in some world, you should be ready to accept your salary going _down_ if the market moves downwards and you're well above the pay to hire a new person.