The second session was just her saying WTF I can't keep track of the location, ownership and tax benefits of 40 accounts!
I've since closed 3/4 of all accounts because of that.
516 karma · joined March 18, 2023
The second session was just her saying WTF I can't keep track of the location, ownership and tax benefits of 40 accounts!
I've since closed 3/4 of all accounts because of that.
There's nothing subjective about not wanting smoke in my lungs. If someone wants to get pot buzzed, go eat an edible and waste a day of productivity for all I care. Smoking the entire house, and costing me my deposit while justifying it with "George Carlin wrote jokes on weed" is peak pothead narcissism that makes me want to have it permanently banned.
There's also a big difference on a social level. Have you ever had a pothead as a roommate? The entire house smells like a garbage dump 24/7. Whereas freshly ground coffee actually smells good. Coffee addicts only bothered me with their unwashed V60s lying around in the sink.
Now I just use the hotdogs as the meeting point.
Maybe I should dump every single child plastic drink/dinnerware for 18/10 stainless steel.
Popular milk bottle brand instructing users how to sterilize their product with the microwave.
Boiling milk bottles is a very common way of sterilization as well.
But I must admit that this is karma. For I have had an almost identical take as you more than a decade ago. Feels like I'm looking in a mirror.
You can opt to keep coding, but it won't get you far in your career. Does this mean the communications have more value than actual implementation? It depends. Again, this value differs at different company sizes.
I just got the chance to code again last month, and I've already completed 5 features (code reviewed) that the juniors couldn't complete in a year. I won't say they are worse at coding, but more that I am more familiar with how dependencies work because I've already done the same thing when I was a junior. Also, knowing who to ask for help also helps a lot.
I stand by my statement. Code is easy and code is cheap. One day you'll understand.
System design at scale? Just trying to convince a separate team to work with us is a nightmare that I get insomnia from.
Coding is the easiest part of my job. FWIW I was just like you when I was a junior dev. Wondering why senior devs and engineering directors can't code. Now I know they can, but their time is better used to negotiate projects so that the junior devs can have their fun. Then I have to take time out to mentor junior devs on how to talk to people without being condescending, because that gets absolutely nothing accomplished in a large company.
Drop any senior dev into coding duty, and their skills return after one to two weeks. On the other hand, asking a junior dev to implement a new system that integrates with 3 other departments, and you'll have to wait two quarters for them just to figure out who to talk to and how to get consensus.
Isn't what you described as The Slog essentially just SMEs? That's not so bad. Perpetual meteoric growth for everyone is not healthy on a macro level. Couple of friends of mine are in what you describe as the worst outcome, yet they can buy houses and put their kids through schools (outside the US).
There's a middle layer of B2B that props up the economy in a more fragmented manner, and I don't think they should be dunked on.
Nowadays we work with way more traffic that incentivizes strict bin packing of traffic within the tightest bounds of the resource pool, with the fastest actuation time. VMs won't give you that. Containerization just makes that so much easier and snappier for large amounts of traffic. But then we had to go global, and orchestrating containers across continents is a PITA. So there's value in k8s for dealing with that. These tools vastly reduce the complexity with regards to managing globally distributed services. But as usual, we start customizing these tools, leading to more complexity.
With that said, I believe startups need to focus on the fastest development and deployment times. So stuff like Docker, Kubernetes or Terraform are entirely unnecessary. As I commented elsewhere before, no one with a total QPS of 10 needs anything beyond GCE or EC2 or on-prem servers. People born in the Cloud age seem to have forgotten that they can just run the cheapest Linux machine with HAProxy and httpd behind a static IP. The focus on always going straight to Cloud complexity, if anything, smells more like engineers in on some VC grift.
Side note: It's hard to hire senior/motivated Java developers. It became a self-fulfilling cycle. Happened somewhere around 2011-2014, no one other than fresh grads graduating from legacy courses still used Java or .NET.
> I realize you don't really care about us vs Adobe, you are going for the best bid.
Er yeah. It's a job. Unless you're OpenAI right now, you'd be hard pressed to find a candidate who means it when they say they love your company vision. It's all theatrics and gate keeping by ego massaging. It's a rite of passage for junior devs to believe words like yours until they find fresh grads earning double their pay, and getting dumped onto the streets during layoffs.
To the junior devs: Passion and enthusiasm are positive attributes for a team's productivity, but they are equally fantastic traits for hiring managers to exploit. Never forget that. From: A very jaded senior engineer who has seen a lot from startups to tech shops to big tech.
Really enhances the debugging experience.
How about the batteries that are required to power a wireless controller? Everything on a patchwork sub needs to be at least n+2 across failure domains. I wouldn't have gone in that sub even with n+5 and a paycheck TBH.
How much money was he trying to save here? Competitive gamers with a way lower net worth stick to tethered controllers for a reason, low latency and reliable connection.
Furthermore, I can believe a bunch of b/millionaires being duped into paying a non-refundable $250k. But I am struggling with the fact that they saw the abyssal porta potty and the BT controller, and still thought it was wise to enter.
The best case scenario here was an 8 hour trip in a space that's worse than long haul Economy to see Titanic ruins on a TV screen. I really don't get the value proposition here.
That poor kid.
But on the other hand, if you gave me one on the plane, I'm definitely putting it on throughout a 14h flight. Anything to let me escape the reality of flying long haul Economy.
We enjoyed (and aced) the classes from the teacher with fewer YOE. Maybe the more experienced teacher was more jaded, maybe the younger teacher was more relatable. Who knows.
I have relatives who are educators their entire lives. One thing I've taken away from listening to them complaining about their work, is that there is an abundance of teachers with long YOE, who are totally checked out from their job, and use their long tenure to bully the younger teachers. There's an idiom they use a lot during these complaints: "Using their tenure to sell their experience."
Finally, it's "you're". Not "your". It was difficult to parse your text when you're not doing it right.
What I deem smart or dumb changes over the years. When I was a junior dev, I saw someone totally new to coding create a single static class method that did tens of thousands of lines of if else checks for a state machine. The group of us junior devs shared the code snippet with each other and laughed at how ridiculous it was. The code could've been so much cleaner with proper extraction and abstraction. The bootcamp fresh minted dev was what I had considered as someone who's dumb but gets things done.
Over the years as I worked with more teams, I've seen people do "smart" things like a one liner quadruple nested ternary return. Everyone marveled at how clean it looked. I've also seen smart devs who experimented with Haskell or OCaml in their spare time start using closures in closures in closures. Lambdas everywhere when remotely possible. Anyone who didn't understand what they were doing were too inexperienced and dumb. They were always heralded as the geniuses of the company.
Nowadays, I very much rather debug a ten thousand line static method with if else clauses. It's quick to navigate, and incredibly easy to debug. Stupidly simple is my new smart.
The only thing I've really concluded after so long is that, the only dumb person in the room is always me. I've been told I'm a pretty kick-ass teacher so that pretty much seals my dumbass status.