Skip Navigation
InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)CM
Posts
0
Comments
25
Joined
2 yr. ago
  • ADHD and easier to type a url than open a new tab. People that can maintain a curated tab list.. I wish my brain would allow it.

    Once a day I close browsers to make sure there’s not some work item I forgot to hit post on.

  • It counts! I remember finally deciding to invest in headphones that I could easily replace the cables first.

    Bluetooth for music is great. Bluetooth turning into “why does my headset change to cruddy codecs 20-30m into a meeting” … no so much!

  • My #1 recommendation is reading https://staffeng.com/book. There’s so much variance between orgs at this level (or worse, implied during a reorg).

    One of the things that book helped me with is understanding the lens others view this level as four separate personas. That unlocked for me that you might be getting advice from people expecting something other than you’re going after.

    Another lens is the product engineering v corp/cloud security world. They can act very differently and you often find these roles straddling 2-3 unique orgs.

    1. Services / customer experience of what your org delivers
    2. Threat modeling mindset: look for the big picture so you can help make sure you can help put emergencies and day to day stuff in context.
    3. Get real feedback from others to put that judgement in perspective. Sometimes they are missing your perspective and other times you are off base!

    Just remember there’s a lot of variance in higher level processes. Read the book above, then read 20 job descriptions for these titles. See if you can understand what they really want from the role.

  • Permanently Deleted

  • Just listened to it again. Highly recommend. The short of it is more searches == more ads == more $. There’s a conflict between a great search experience (landing not on google) versus the time you spend ON Google.

    Great story and just terrible outcome.

  • The closest I ever got to this story was working help desk in 1996. A user called up saying they had deleted the Internet.

    Took me a while to understand he dragged “the Internet” to the recycle bin on the desktop.

  • IReal pro for chord charts and backing practice.

    Chord AI is good for “what’s the chords in this YouTube video”

    https://www.sheetmusicscanner.com is useful for I have sheet music I want to put into guitar pro on the desktop.

    Scan; export as musicml; import on desktop. Cleanup.

    8Strummer - getting new strum pattens down can be a challenge and this gives a useful visual

  • Glad you got diagnosed. There’s a ton of bad management in startups. Especially stay away from managers that grew up in toxic shops.

    I’ve always been a strong employee. People get good at pushing buttons. Spent more time in a divorce therapy talking about a manager than the personal issues.

    Realized for every boundary problem I had, there were n alienated people on my team that really got hurt hard. Sr. Management fixed the issue

    Be good at taking breaks. Be good at looking for new roles before you need them.

    Often; the money side that seems big to employees is new house rich. If you aren’t happy, it’s not worth it.

  • You mentioned 6-7h of sleep. I suspect you aren’t getting enough sleep and not stretching enough.

    You said you went from sedentary to active. Do you have off peak weeks? Did you just start leg days? Is it muscle pain or joint pain? Do you stretch?

    Your tendons and joints need time to build up. I suspect you did wide ranges, you’ve not been stretching, and you’ve really put a strain on the muscle ends. Stretch daily and move throw your motions.

    I went through a similar relearning curve going from cycling -> cycling / yoga -> adding weights

    If the stretching activity isn’t there, man the recovery sucks.

    Good for you for doing it! You’ll figure it out!

  • Read, reproduce, understand. Think of how the programmer was solving a problem and left a problem. Did they probably didn’t understand the problems. The synthetic challenges are often a skill to themselves.

    Re attention span, consider different expectations. Professional product engagements are often 2 ftes/2 weeks. Getting a few good findings out in that time is the goal.

    Sometimes they run out of time on a thread they are looking at. Sometimes they pull on a thread only to find out there’s no way from here. Sometimes years later there’s an insight that x could work.

    Building up that last skill is what makes you more effective. Find someone to bounce ideas off of that’s in the learning curve with you.