• 0 Posts
  • 120 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle



  • This feels like a troll account for some reason. Stirring the pot pretty disingenuously across the board.

    The railroad workers got what they wanted because the admin followed up. So he averted a rail strike and got them their concessions.

    The east Palestine disaster isn’t this admins fault. It’s anl negligent rail companies fault combined with deregulation from previous Congresses and the previous administration. Not to mention both previous Congress and admin sat on an infrastructure spending packages that could have addressed antiquated rail infrastructure. Ironically, Biden managed to pass the biggest infrastructure package in American history (with a divided Congress). With clean energy and resiliency built it. And if I recall correctly FEMA and Co are still monitoring and supporting the clean up.

    Your fossil fuel is thing is BS because of course its growing–we’ve done nothing, our CONGRESS has done nothing to curtail it. The previous admin opened the flood gates on regulations as well. Don’t lay that at the feet of this admin. That’s absolute horse shit. The aforementioned infrastructure bill included the most investment in green energy ever.

    And the anti trans shit is Bidens fault how? He signed the respect marriage act, he reversed the ban for trans service members, and strengthen some of the protections against discrimination re housing and healthcare.

    You want lord emperor Biden to go send mobs after statehouses and local governments?? That’s not how Any of this works and you know it.




  • Nix is the vim of package management but without good documentation. So it’s incredibly powerful and useful once you get into it, but imagine trying to learn vim without any docs or guidance. Vim has a steep learning curve with good documentation, YouTube tutorials, blog posts, and forum guides.

    Nix doesn’t really have a wealth of that.

    That’s nix package management and nixos in a nutshell.





  • That’s a great point. But vsphere not being available in the free tier kind of proves my point. Why hamstring your free tier by eliminating the more useful features? I understand not giving away your product for free but there was a way to do it where you turn it into a marketing tool.

    You drive people away and then you end up in a situation where “esxi free tier is pointless” and then you kill that and all your goodwill completely. I guess we’ll see how it plays out.

    Broadcom isn’t know for being great with acquisitions. It’s probably going to strip it for parts and sell it off.


  • Maybe some MBA did the math and is smarter than me or maybe they have different goals for esxi that extend beyond (having people and companies use it), but they have to realize free tier esxi is what the nerds and IT pros are going to use to hone their skills. And then those are the people that talk their companies into buying products.

    Moves like this always seem so short sighted. 5 years from now you are going to see an uptick in proxmox setups or managed solutions using proxmox and other competitors.


  • I work mostly remote now, but I had a week long leadership “off-site” meeting. It was probably okay to be casual.

    My wife was shocked when I wore my suit (no tie).

    But it’s easy. It’s my uniform. They were already dry cleaned, I don’t have to think about it in the morning, it’s comfortable, and like you said, you don’t have to worry about being under or over dressed. I just lose the jacket and roll up my sleeves and it’s business casual. Throw on a tie and I could brief the CEO.



  • There are different audiences for demos though. It should be that way at the “working level”. When you start moving up the chain with more senior leadership in your org, it starts to make more sense to have the PM do the demos/briefs.

    Usually devs don’t particularly care or want to and sometimes they aren’t really qualified to–its not their skillset. But if it’s a good PM, that’s where they shine. That’s the value they bring to the project. They (should) know the politics, landmines, things that specific leaders would care about (and to highlight for them), and how to frame it to current business needs. They have the context to understand when a seemingly innocuous question is actually pointed. They might not know the intricacies of your code, but they (should) know the intricacies of the organization. That’s not something most developers know, and why should they? That’s not their job.

    Sometimes it even involves groundwork meetings and demos to make sure you have support from other key components in your org-- like getting your CTO excited because one of his performance goals was x and your project is the first real implementation of x. Now, you have the CTO ready to speak on your behalf in front of the CIO. As a PM you know that the CIO has been getting flack from the CFO because there hasn’t been a good way to capture costs for Y, but your system starts the org down the path to fix that. Now they are both excited about the project and in your corner. Etc etc