Being passionate about what you do and understanding what you can really get out of it

A broad range of behaviors and commitments happen when working beyond what you thought was possible, building a team with a passion, and building things bigger than yourself.  The best parts of that aren't what you build even though that is amazing. The best part is the experience gained and the relationships built with people you can't believe you get to work with.

Companies don't care about individuals and will push you out the door and find someone fresher without a thought. The company lives for the company. Billionaires live to be bigger billionaires. You have to protect your mind and your health. When you inevitably leave, you will take the experience, memories, and co-workers you hope to meet in future work lives.  

YouTube Version

When I love every day at work I think this:
  • "hard work"
  • "I'm one of the lucky people who loves what they do"
  • "creating things/work is a passion"
  • "Working with passion is the only way"
  • "I'm working with people who are interested"
  • "I hope I can hold up my part while working with amazing people"
  • “What can we do to make this better”
When I think of passion-draining gigs I think of this.
  • "40 hours a week"
  • "phoning it in"
  • "Faking it"
  • "Heads down"
  • "Meetings without end"
  • "No one can say yes"
  • “The team is doing the least possible to get credit”
When Musk says hard work I think this:
  • "feeding the billionaire instead of your soul”.
  • "sleeping on the floor in the office"
  • "abandoning your family"
  • "permanent death march to burnout"
I've worked at a range of places; the best were those where passion was rewarded and stuff was built.  It wasn't the place where people were insulted into commitment or quitting.

Video

Revision History

2022 02

Comments

Post a Comment

Popular posts from this blog

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI
Read more

DNS for Azure Point to Site (P2S) VPN - getting the internal IPs

Image
I wanted to access all my Azure resources without making any of them visible to the Internet.   The easiest give my local machine access to everything on my Azure Virtual Network (VNET) was to connect to it over VPN. It turns out creating Azure VPN gateways and connecting to Azure VPN endpoints is easy.  There are some subtleties in getting DNS name resolution to work that can confuse when first starting out. Setting the Stage There are a few ways to get to Azure endpoints and resources that are blocked from the internet.  We can  Create a Point-to-Site connection from our local machines to Azure Network Gateways Create a Site-to-Site network connection from our local networks to Azure Network Gateways. Use Bastion Hosts Use Cloud Shell Leave everything open to the internet. I chose a Point-to-Site (P2S) VPN connection that connects from my laptop to a VNet Gateway.  That joins my laptop
Read more