home.social

#firstup — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #firstup, aggregated by home.social.

  1. CW: Article: Once You're Asking the Right Question, You Don't Need To Ask!

    The other week, a coding LLM helped me... without me ever submitting a single prompt to it. I just typed into it all the component parts of my problem, and in doing so the solution revealed itself to me. It's rubberducking... silent AI edition!
    Read more: danq.me/2026/04/26/ai-rubber-d

    #article #ai #comics #debugging #firstup #programming #work

  2. What breaks when one of your developers leaves?

    On Friday, I said goodbye to a colleague as she left us after most of a decade with the company. Then this morning, all hell broke loose on some production servers.

    It turns out that the API key that connected our application to our feature flag management platform was associated with her account, and hadn't shown up in the exit audit.

    Let this be your reminder to go check where, if anywhere, your applications are using person-specific keys where they should be using generic ones!

    #note #work #firstup #software #programming #devops

    Via: 🔗 danq.me/2026/04/20/what-breaks/

  3. What breaks when one of your developers leaves?

    On Friday, I said goodbye to a colleague as she left us after most of a decade with the company. Then this morning, all hell broke loose on some production servers.

    It turns out that the API key that connected our application to our feature flag management platform was associated with her account, and hadn't shown up in the exit audit.

    Let this be your reminder to go check where, if anywhere, your applications are using person-specific keys where they should be using generic ones!

    #note #work #firstup #software #programming #devops

    Via: 🔗 danq.me/2026/04/20/what-breaks/

  4. What breaks when one of your developers leaves?

    On Friday, I said goodbye to a colleague as she left us after most of a decade with the company. Then this morning, all hell broke loose on some production servers.

    It turns out that the API key that connected our application to our feature flag management platform was associated with her account, and hadn't shown up in the exit audit.

    Let this be your reminder to go check where, if anywhere, your applications are using person-specific keys where they should be using generic ones!

    #note #work #firstup #software #programming #devops

    Via: 🔗 danq.me/2026/04/20/what-breaks/

  5. What breaks when one of your developers leaves?

    On Friday, I said goodbye to a colleague as she left us after most of a decade with the company. Then this morning, all hell broke loose on some production servers.

    It turns out that the API key that connected our application to our feature flag management platform was associated with her account, and hadn't shown up in the exit audit.

    Let this be your reminder to go check where, if anywhere, your applications are using person-specific keys where they should be using generic ones!

    #note #work #firstup #software #programming #devops

    Via: 🔗 danq.me/2026/04/20/what-breaks/

  6. What breaks when one of your developers leaves?

    On Friday, I said goodbye to a colleague as she left us after most of a decade with the company. Then this morning, all hell broke loose on some production servers.

    It turns out that the API key that connected our application to our feature flag management platform was associated with her account, and hadn't shown up in the exit audit.

    Let this be your reminder to go check where, if anywhere, your applications are using person-specific keys where they should be using generic ones!

    #note #work #firstup #software #programming #devops

    Via: 🔗 danq.me/2026/04/20/what-breaks/

  7. By way of a #GoodFork...

    I have #AnotherGoodStory about #EducatingPeople; you #Might #LikeIT, you #MostProbably won't...

    #FirstUp: Some #TrueFacts for #Context:

    1: I made my #MusicTeacher cry;
    2: I was #Only14 #AtTheTime; and,
    3: #NoOneCares

    #MakeYourselves #Comfortable; this #Thread could #GoOn for #QuiteSomeTime...

    #GrabACoffee; maybe a #Biscuit...

    🧙☕🤖:wolfparty:​🤖☕🧙 | :fediverse:​🦹:PirateBadge:​​🦄​:PirateBadge:​​🦹:fediverse:

  8. Off to my first day at Firstup. Gotta have an induction: get my ID badge, learn where the toilets are, how to refill the coffee machine, and all that jazz.

    Except, of course, none of those steps will be part of my induction. Because, yet again, I've taken a remote-first position. I'm 100% sold that, for me, remote/distributed work helps me bring my most-productive self. It might not be for everybody, but it's great for me.

    And now: I'm going to find out where the water cooler is. No, wait... some other thing!

    #note #firstup #work #job #employment #telecommuting #teleworking

    Via: 🔗 danq.me/2025/07/14/firstup-day

  9. Today, an AI review tool used by my workplace reviewed some code that I wrote, and incorrectly claimed that it would introduce a bug because a global variable I created could "be available to multiple browser tabs" (that's not how browser JavaScript works).

    Just in case I was mistaken, I explained to the AI why I thought it was wrong, and asked it to explain itself.

    To do so, the LLM wrote a PR to propose adding some code to use our application's save mechanism to pass the data back, via the server, and to any other browser tab, thereby creating the problem that it claimed existed.

    This isn't even the most-efficient way to create this problem. localStorage would have been better.

    So in other words, today I watched an AI:
    (a) claim to have discovered a problem (that doesn't exist),
    (b) when challenged, attempt to create the problem (that wasn't needed), and
    (c) do so in a way that was suboptimal.

    Humans aren't perfect. A human could easily make one of these mistakes. Under some circumstances, a human might even have made two of these mistakes. But to make all three? That took an AI.

    What's the old saying? "To err is human, but to really foul things up you need a computer."

    #note #ai #work #firstup #programming #javascript

    Via: 🔗 danq.me/2026/02/25/to-really-f

  10. Today, an AI review tool used by my workplace reviewed some code that I wrote, and incorrectly claimed that it would introduce a bug because a global variable I created could "be available to multiple browser tabs" (that's not how browser JavaScript works).

    Just in case I was mistaken, I explained to the AI why I thought it was wrong, and asked it to explain itself.

    To do so, the LLM wrote a PR to propose adding some code to use our application's save mechanism to pass the data back, via the server, and to any other browser tab, thereby creating the problem that it claimed existed.

    This isn't even the most-efficient way to create this problem. localStorage would have been better.

    So in other words, today I watched an AI:
    (a) claim to have discovered a problem (that doesn't exist),
    (b) when challenged, attempt to create the problem (that wasn't needed), and
    (c) do so in a way that was suboptimal.

    Humans aren't perfect. A human could easily make one of these mistakes. Under some circumstances, a human might even have made two of these mistakes. But to make all three? That took an AI.

    What's the old saying? "To err is human, but to really foul things up you need a computer."

    #note #ai #work #firstup #programming #javascript

    Via: 🔗 danq.me/2026/02/25/to-really-f

  11. Today, an AI review tool used by my workplace reviewed some code that I wrote, and incorrectly claimed that it would introduce a bug because a global variable I created could "be available to multiple browser tabs" (that's not how browser JavaScript works).

    Just in case I was mistaken, I explained to the AI why I thought it was wrong, and asked it to explain itself.

    To do so, the LLM wrote a PR to propose adding some code to use our application's save mechanism to pass the data back, via the server, and to any other browser tab, thereby creating the problem that it claimed existed.

    This isn't even the most-efficient way to create this problem. localStorage would have been better.

    So in other words, today I watched an AI:
    (a) claim to have discovered a problem (that doesn't exist),
    (b) when challenged, attempt to create the problem (that wasn't needed), and
    (c) do so in a way that was suboptimal.

    Humans aren't perfect. A human could easily make one of these mistakes. Under some circumstances, a human might even have made two of these mistakes. But to make all three? That took an AI.

    What's the old saying? "To err is human, but to really foul things up you need a computer."

    #note #ai #work #firstup #programming #javascript

    Via: 🔗 danq.me/2026/02/25/to-really-f

  12. Today, an AI review tool used by my workplace reviewed some code that I wrote, and incorrectly claimed that it would introduce a bug because a global variable I created could "be available to multiple browser tabs" (that's not how browser JavaScript works).

    Just in case I was mistaken, I explained to the AI why I thought it was wrong, and asked it to explain itself.

    To do so, the LLM wrote a PR to propose adding some code to use our application's save mechanism to pass the data back, via the server, and to any other browser tab, thereby creating the problem that it claimed existed.

    This isn't even the most-efficient way to create this problem. localStorage would have been better.

    So in other words, today I watched an AI:
    (a) claim to have discovered a problem (that doesn't exist),
    (b) when challenged, attempt to create the problem (that wasn't needed), and
    (c) do so in a way that was suboptimal.

    Humans aren't perfect. A human could easily make one of these mistakes. Under some circumstances, a human might even have made two of these mistakes. But to make all three? That took an AI.

    What's the old saying? "To err is human, but to really foul things up you need a computer."

    #note #ai #work #firstup #programming #javascript

    Via: 🔗 danq.me/2026/02/25/to-really-f

  13. Today, an AI review tool used by my workplace reviewed some code that I wrote, and incorrectly claimed that it would introduce a bug because a global variable I created could "be available to multiple browser tabs" (that's not how browser JavaScript works).

    Just in case I was mistaken, I explained to the AI why I thought it was wrong, and asked it to explain itself.

    To do so, the LLM wrote a PR to propose adding some code to use our application's save mechanism to pass the data back, via the server, and to any other browser tab, thereby creating the problem that it claimed existed.

    This isn't even the most-efficient way to create this problem. localStorage would have been better.

    So in other words, today I watched an AI:
    (a) claim to have discovered a problem (that doesn't exist),
    (b) when challenged, attempt to create the problem (that wasn't needed), and
    (c) do so in a way that was suboptimal.

    Humans aren't perfect. A human could easily make one of these mistakes. Under some circumstances, a human might even have made two of these mistakes. But to make all three? That took an AI.

    What's the old saying? "To err is human, but to really foul things up you need a computer."

    #note #ai #work #firstup #programming #javascript

    Via: 🔗 danq.me/2026/02/25/to-really-f

  14. Highlight of my workday was debugging an issue that turned out to be nothing like what the reporter had diagnosed.

    The report suggested that our system was having problems parsing URLs with colons in the pathname, suggesting perhaps an encoding issue. It wasn't until I took a deep dive into the logs that I realised that this was a secondary characteristic of many URLs found in customers' SharePoint installations. And many of those URLs get redirected. And SharePoint often uses relative URLs when it sends redirections. And it turned out that our systems' redirect handler... wasn't correctly handling relative URLs.

    It all turned into a hundred line automated test to mock SharePoint and demonstrate the problem... followed by a tiny two-line fix to the actual code. And probably the most-satisfying part of my workday!

    #note #testing #http #web #ruby #firstup #work #programming

    Via: 🔗 danq.me/2026/01/28/mocking-sha

  15. Highlight of my workday was debugging an issue that turned out to be nothing like what the reporter had diagnosed.

    The report suggested that our system was having problems parsing URLs with colons in the pathname, suggesting perhaps an encoding issue. It wasn't until I took a deep dive into the logs that I realised that this was a secondary characteristic of many URLs found in customers' SharePoint installations. And many of those URLs get redirected. And SharePoint often uses relative URLs when it sends redirections. And it turned out that our systems' redirect handler... wasn't correctly handling relative URLs.

    It all turned into a hundred line automated test to mock SharePoint and demonstrate the problem... followed by a tiny two-line fix to the actual code. And probably the most-satisfying part of my workday!

    #note #testing #http #web #ruby #firstup #work #programming

    Via: 🔗 danq.me/2026/01/28/mocking-sha

  16. Highlight of my workday was debugging an issue that turned out to be nothing like what the reporter had diagnosed.

    The report suggested that our system was having problems parsing URLs with colons in the pathname, suggesting perhaps an encoding issue. It wasn't until I took a deep dive into the logs that I realised that this was a secondary characteristic of many URLs found in customers' SharePoint installations. And many of those URLs get redirected. And SharePoint often uses relative URLs when it sends redirections. And it turned out that our systems' redirect handler... wasn't correctly handling relative URLs.

    It all turned into a hundred line automated test to mock SharePoint and demonstrate the problem... followed by a tiny two-line fix to the actual code. And probably the most-satisfying part of my workday!

    #note #testing #http #web #ruby #firstup #work #programming

    Via: 🔗 danq.me/2026/01/28/mocking-sha

  17. Highlight of my workday was debugging an issue that turned out to be nothing like what the reporter had diagnosed.

    The report suggested that our system was having problems parsing URLs with colons in the pathname, suggesting perhaps an encoding issue. It wasn't until I took a deep dive into the logs that I realised that this was a secondary characteristic of many URLs found in customers' SharePoint installations. And many of those URLs get redirected. And SharePoint often uses relative URLs when it sends redirections. And it turned out that our systems' redirect handler... wasn't correctly handling relative URLs.

    It all turned into a hundred line automated test to mock SharePoint and demonstrate the problem... followed by a tiny two-line fix to the actual code. And probably the most-satisfying part of my workday!

    #note #testing #http #web #ruby #firstup #work #programming

    Via: 🔗 danq.me/2026/01/28/mocking-sha

  18. Highlight of my workday was debugging an issue that turned out to be nothing like what the reporter had diagnosed.

    The report suggested that our system was having problems parsing URLs with colons in the pathname, suggesting perhaps an encoding issue. It wasn't until I took a deep dive into the logs that I realised that this was a secondary characteristic of many URLs found in customers' SharePoint installations. And many of those URLs get redirected. And SharePoint often uses relative URLs when it sends redirections. And it turned out that our systems' redirect handler... wasn't correctly handling relative URLs.

    It all turned into a hundred line automated test to mock SharePoint and demonstrate the problem... followed by a tiny two-line fix to the actual code. And probably the most-satisfying part of my workday!

    #note #testing #http #web #ruby #firstup #work #programming

    Via: 🔗 danq.me/2026/01/28/mocking-sha

  19. In my first few weeks at my new employer, my code contributions have added 218 lines of code, deleted 2,663. Only one of my PRs has resulted in a net increase in the size of their codebases (by two lines).

    I need to pick up the pace if I'm going to reach the ultimate goal of deleting ALL of the code within my lifetime. (That's the ultimate aim, right?)

    #note #firstup #job #work #programming #github #sourceControl #employment

    Via: 🔗 danq.me/2025/08/01/26999/

  20. In my first few weeks at my new employer, my code contributions have added 218 lines of code, deleted 2,663. Only one of my PRs has resulted in a net increase in the size of their codebases (by two lines).

    I need to pick up the pace if I'm going to reach the ultimate goal of deleting ALL of the code within my lifetime. (That's the ultimate aim, right?)

    #note #firstup #job #work #programming #github #sourceControl #employment

    Via: 🔗 danq.me/2025/08/01/26999/

  21. In my first few weeks at my new employer, my code contributions have added 218 lines of code, deleted 2,663. Only one of my PRs has resulted in a net increase in the size of their codebases (by two lines).

    I need to pick up the pace if I'm going to reach the ultimate goal of deleting ALL of the code within my lifetime. (That's the ultimate aim, right?)

    #note #firstup #job #work #programming #github #sourceControl #employment

    Via: 🔗 danq.me/2025/08/01/26999/

  22. In my first few weeks at my new employer, my code contributions have added 218 lines of code, deleted 2,663. Only one of my PRs has resulted in a net increase in the size of their codebases (by two lines).

    I need to pick up the pace if I'm going to reach the ultimate goal of deleting ALL of the code within my lifetime. (That's the ultimate aim, right?)

    #note #firstup #job #work #programming #github #sourceControl #employment

    Via: 🔗 danq.me/2025/08/01/26999/

  23. In my first few weeks at my new employer, my code contributions have added 218 lines of code, deleted 2,663. Only one of my PRs has resulted in a net increase in the size of their codebases (by two lines).

    I need to pick up the pace if I'm going to reach the ultimate goal of deleting ALL of the code within my lifetime. (That's the ultimate aim, right?)

    #note #firstup #job #work #programming #github #sourceControl #employment

    Via: 🔗 danq.me/2025/08/01/26999/

  24. I spent most of a day getting my new development environment set up, because I kept hitting issues that nobody at my new employer had experienced before. A "perfect storm" of coincidences that conspired together to completely wreck my chance of a simple setup.

    The factors?
    - Apple's M4 processors remove the SVE architecture and its instruction set, which was present in the M1 through M3
    - The Colima dockerisation tool still reports to arm64 containers that SVE is available
    - Java < 24 will, by default, use SVE for some functions if it's told that it's available
    - Opensearch 2.x will not run on Java > 23

    If ANY ONE of those statements were not true, I wouldn't have had any trouble. But the combination of all four of them meant that I was getting proper segfault-death crashes.

    I blame Apple. Who removes instructions from a processor within the same family‽ (I'm sure that in reality there's probably some important reason for it that's beyond my ken, but still!)

    #note #apple #programming #computers #technology #docker #firstup #job #work #employment #java

    Via: 🔗 danq.me/2025/07/16/m4-colima-s

  25. I spent most of a day getting my new development environment set up, because I kept hitting issues that nobody at my new employer had experienced before. A "perfect storm" of coincidences that conspired together to completely wreck my chance of a simple setup.

    The factors?
    - Apple's M4 processors remove the SVE architecture and its instruction set, which was present in the M1 through M3
    - The Colima dockerisation tool still reports to arm64 containers that SVE is available
    - Java < 24 will, by default, use SVE for some functions if it's told that it's available
    - Opensearch 2.x will not run on Java > 23

    If ANY ONE of those statements were not true, I wouldn't have had any trouble. But the combination of all four of them meant that I was getting proper segfault-death crashes.

    I blame Apple. Who removes instructions from a processor within the same family‽ (I'm sure that in reality there's probably some important reason for it that's beyond my ken, but still!)

    #note #apple #programming #computers #technology #docker #firstup #job #work #employment #java

    Via: 🔗 danq.me/2025/07/16/m4-colima-s

  26. I spent most of a day getting my new development environment set up, because I kept hitting issues that nobody at my new employer had experienced before. A "perfect storm" of coincidences that conspired together to completely wreck my chance of a simple setup.

    The factors?
    - Apple's M4 processors remove the SVE architecture and its instruction set, which was present in the M1 through M3
    - The Colima dockerisation tool still reports to arm64 containers that SVE is available
    - Java < 24 will, by default, use SVE for some functions if it's told that it's available
    - Opensearch 2.x will not run on Java > 23

    If ANY ONE of those statements were not true, I wouldn't have had any trouble. But the combination of all four of them meant that I was getting proper segfault-death crashes.

    I blame Apple. Who removes instructions from a processor within the same family‽ (I'm sure that in reality there's probably some important reason for it that's beyond my ken, but still!)

    #note #apple #programming #computers #technology #docker #firstup #job #work #employment #java

    Via: 🔗 danq.me/2025/07/16/m4-colima-s

  27. I spent most of a day getting my new development environment set up, because I kept hitting issues that nobody at my new employer had experienced before. A "perfect storm" of coincidences that conspired together to completely wreck my chance of a simple setup.

    The factors?
    - Apple's M4 processors remove the SVE architecture and its instruction set, which was present in the M1 through M3
    - The Colima dockerisation tool still reports to arm64 containers that SVE is available
    - Java < 24 will, by default, use SVE for some functions if it's told that it's available
    - Opensearch 2.x will not run on Java > 23

    If ANY ONE of those statements were not true, I wouldn't have had any trouble. But the combination of all four of them meant that I was getting proper segfault-death crashes.

    I blame Apple. Who removes instructions from a processor within the same family‽ (I'm sure that in reality there's probably some important reason for it that's beyond my ken, but still!)

    #note #apple #programming #computers #technology #docker #firstup #job #work #employment #java

    Via: 🔗 danq.me/2025/07/16/m4-colima-s

  28. I spent most of a day getting my new development environment set up, because I kept hitting issues that nobody at my new employer had experienced before. A "perfect storm" of coincidences that conspired together to completely wreck my chance of a simple setup.

    The factors?
    - Apple's M4 processors remove the SVE architecture and its instruction set, which was present in the M1 through M3
    - The Colima dockerisation tool still reports to arm64 containers that SVE is available
    - Java < 24 will, by default, use SVE for some functions if it's told that it's available
    - Opensearch 2.x will not run on Java > 23

    If ANY ONE of those statements were not true, I wouldn't have had any trouble. But the combination of all four of them meant that I was getting proper segfault-death crashes.

    I blame Apple. Who removes instructions from a processor within the same family‽ (I'm sure that in reality there's probably some important reason for it that's beyond my ken, but still!)

    #note #apple #programming #computers #technology #docker #firstup #job #work #employment #java

    Via: 🔗 danq.me/2025/07/16/m4-colima-s

  29. Off to my first day at Firstup. Gotta have an induction: get my ID badge, learn where the toilets are, how to refill the coffee machine, and all that jazz.

    Except, of course, none of those steps will be part of my induction. Because, yet again, I've taken a remote-first position. I'm 100% sold that, for me, remote/distributed work helps me bring my most-productive self. It might not be for everybody, but it's great for me.

    And now: I'm going to find out where the water cooler is. No, wait... some other thing!

    #note #firstup #work #job #employment #telecommuting #teleworking

    Via: 🔗 danq.me/2025/07/14/firstup-day

  30. Off to my first day at Firstup. Gotta have an induction: get my ID badge, learn where the toilets are, how to refill the coffee machine, and all that jazz.

    Except, of course, none of those steps will be part of my induction. Because, yet again, I've taken a remote-first position. I'm 100% sold that, for me, remote/distributed work helps me bring my most-productive self. It might not be for everybody, but it's great for me.

    And now: I'm going to find out where the water cooler is. No, wait... some other thing!

    #note #firstup #work #job #employment #telecommuting #teleworking

    Via: 🔗 danq.me/2025/07/14/firstup-day

  31. Off to my first day at Firstup. Gotta have an induction: get my ID badge, learn where the toilets are, how to refill the coffee machine, and all that jazz.

    Except, of course, none of those steps will be part of my induction. Because, yet again, I've taken a remote-first position. I'm 100% sold that, for me, remote/distributed work helps me bring my most-productive self. It might not be for everybody, but it's great for me.

    And now: I'm going to find out where the water cooler is. No, wait... some other thing!

    #note #firstup #work #job #employment #telecommuting #teleworking

    Via: 🔗 danq.me/2025/07/14/firstup-day

  32. Off to my first day at Firstup. Gotta have an induction: get my ID badge, learn where the toilets are, how to refill the coffee machine, and all that jazz.

    Except, of course, none of those steps will be part of my induction. Because, yet again, I've taken a remote-first position. I'm 100% sold that, for me, remote/distributed work helps me bring my most-productive self. It might not be for everybody, but it's great for me.

    And now: I'm going to find out where the water cooler is. No, wait... some other thing!

    #note #firstup #work #job #employment #telecommuting #teleworking

    Via: 🔗 danq.me/2025/07/14/firstup-day

  33. "[Shane] Jones said his plan was to marginalise 'the gatekeepers hiding behind the Wildlife Act, the people trying to turn DOC into some sort of preservationist state and deny New Zealand as a livelihood'."

    #FirstUp, 2025

    rnz.co.nz/news/political/54052

    Oh believe me Shame, we'll be lying in front of the bulldozers if it comes to that, not hiding behind them. You don't seem to understand how environmental law protects you and your ecocidal bankrollers from us, not the other way around.

    #conservation

  34. "[Shane] Jones said his plan was to marginalise 'the gatekeepers hiding behind the Wildlife Act, the people trying to turn DOC into some sort of preservationist state and deny New Zealand as a livelihood'."

    #FirstUp, 2025

    rnz.co.nz/news/political/54052

    Oh believe me Shame, we'll be lying in front of the bulldozers if it comes to that, not hiding behind them. You don't seem to understand how environmental law protects you and your ecocidal bankrollers from us, not the other way around.

    #conservation

  35. "[Shane] Jones said his plan was to marginalise 'the gatekeepers hiding behind the Wildlife Act, the people trying to turn DOC into some sort of preservationist state and deny New Zealand as a livelihood'."

    #FirstUp, 2025

    rnz.co.nz/news/political/54052

    Oh believe me Shame, we'll be lying in front of the bulldozers if it comes to that, not hiding behind them. You don't seem to understand how environmental law protects you and your ecocidal bankrollers from us, not the other way around.

    #conservation

  36. "[Shane] Jones said his plan was to marginalise 'the gatekeepers hiding behind the Wildlife Act, the people trying to turn DOC into some sort of preservationist state and deny New Zealand as a livelihood'."

    #FirstUp, 2025

    rnz.co.nz/news/political/54052

    Oh believe me Shame, we'll be lying in front of the bulldozers if it comes to that, not hiding behind them. You don't seem to understand how environmental law protects you and your ecocidal bankrollers from us, not the other way around.

    #conservation