home.social

#blindcoding — Public Fediverse posts

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

  1. 🛎️ Blind Coding Is Coming

    "If full blind coding holds, the operating unit is no longer a team but a loop. Software companies compress into objective setting plus compute. The first truly autonomous, no human company becomes viable."

    aisecret.us/blind-coding-is-co

    #BlindCoding #AutonomousSoftware #TechInnovation #FutureOfWork

  2. 🛎️ Blind Coding Is Coming

    "If full blind coding holds, the operating unit is no longer a team but a loop. Software companies compress into objective setting plus compute. The first truly autonomous, no human company becomes viable."

    aisecret.us/blind-coding-is-co

  3. 🛎️ Blind Coding Is Coming

    "If full blind coding holds, the operating unit is no longer a team but a loop. Software companies compress into objective setting plus compute. The first truly autonomous, no human company becomes viable."

    aisecret.us/blind-coding-is-co

    #BlindCoding #AutonomousSoftware #TechInnovation #FutureOfWork

  4. 🛎️ Blind Coding Is Coming

    "If full blind coding holds, the operating unit is no longer a team but a loop. Software companies compress into objective setting plus compute. The first truly autonomous, no human company becomes viable."

    aisecret.us/blind-coding-is-co

    #BlindCoding #AutonomousSoftware #TechInnovation #FutureOfWork

  5. 🛎️ Blind Coding Is Coming

    "If full blind coding holds, the operating unit is no longer a team but a loop. Software companies compress into objective setting plus compute. The first truly autonomous, no human company becomes viable."

    aisecret.us/blind-coding-is-co

    #BlindCoding #AutonomousSoftware #TechInnovation #FutureOfWork

  6. 🛎️ Blind Coding Is Coming

    "If full blind coding holds, the operating unit is no longer a team but a loop. Software companies compress into objective setting plus compute. The first truly autonomous, no human company becomes viable."

    aisecret.us/blind-coding-is-co

    #BlindCoding #AutonomousSoftware #TechInnovation #FutureOfWork

  7. Using #Codex, I started making it draft an ongoing document explaining the How and Why of the changes and updates it was making through each milestone of a project. This lets me follow along and learn about coding practices rather than just asking for things and having them magically happen. It also adds #AI accountability, because it does inevitably create bugs, and rewrite mistakes, and the #accessible markdown doc is easier to read than a standard change log. #Blind #BlindCoding

  8. Using #Codex, I started making it draft an ongoing document explaining the How and Why of the changes and updates it was making through each milestone of a project. This lets me follow along and learn about coding practices rather than just asking for things and having them magically happen. It also adds #AI accountability, because it does inevitably create bugs, and rewrite mistakes, and the #accessible markdown doc is easier to read than a standard change log. #Blind #BlindCoding

  9. Using #Codex, I started making it draft an ongoing document explaining the How and Why of the changes and updates it was making through each milestone of a project. This lets me follow along and learn about coding practices rather than just asking for things and having them magically happen. It also adds #AI accountability, because it does inevitably create bugs, and rewrite mistakes, and the #accessible markdown doc is easier to read than a standard change log. #Blind #BlindCoding

  10. Using , I started making it draft an ongoing document explaining the How and Why of the changes and updates it was making through each milestone of a project. This lets me follow along and learn about coding practices rather than just asking for things and having them magically happen. It also adds accountability, because it does inevitably create bugs, and rewrite mistakes, and the markdown doc is easier to read than a standard change log.

  11. Using #Codex, I started making it draft an ongoing document explaining the How and Why of the changes and updates it was making through each milestone of a project. This lets me follow along and learn about coding practices rather than just asking for things and having them magically happen. It also adds #AI accountability, because it does inevitably create bugs, and rewrite mistakes, and the #accessible markdown doc is easier to read than a standard change log. #Blind #BlindCoding

  12. When vibe coding or co-coding with #AI, always keep track of your source control. I've learned to git commit early and often with each step, and to only share compiling code with the AI to help prevent doom spirals of patches and errors when it tries to solve for it's own mistakes. Be comfy with git reset, the git patching process, and paying close attention to exactly how the AI is interpreting your psuedo code and instructions, especially with big updates and refactors. #BlindCoding

  13. When vibe coding or co-coding with #AI, always keep track of your source control. I've learned to git commit early and often with each step, and to only share compiling code with the AI to help prevent doom spirals of patches and errors when it tries to solve for it's own mistakes. Be comfy with git reset, the git patching process, and paying close attention to exactly how the AI is interpreting your psuedo code and instructions, especially with big updates and refactors. #BlindCoding

  14. When vibe coding or co-coding with #AI, always keep track of your source control. I've learned to git commit early and often with each step, and to only share compiling code with the AI to help prevent doom spirals of patches and errors when it tries to solve for it's own mistakes. Be comfy with git reset, the git patching process, and paying close attention to exactly how the AI is interpreting your psuedo code and instructions, especially with big updates and refactors. #BlindCoding

  15. When vibe coding or co-coding with , always keep track of your source control. I've learned to git commit early and often with each step, and to only share compiling code with the AI to help prevent doom spirals of patches and errors when it tries to solve for it's own mistakes. Be comfy with git reset, the git patching process, and paying close attention to exactly how the AI is interpreting your psuedo code and instructions, especially with big updates and refactors.

  16. When vibe coding or co-coding with #AI, always keep track of your source control. I've learned to git commit early and often with each step, and to only share compiling code with the AI to help prevent doom spirals of patches and errors when it tries to solve for it's own mistakes. Be comfy with git reset, the git patching process, and paying close attention to exactly how the AI is interpreting your psuedo code and instructions, especially with big updates and refactors. #BlindCoding

  17. I'm finally sitting down and working my way through #100DaysOfSwift, and have passed checkpoint 5 and managed to get through Closures. My M3 Pro is making learning this much...um...Swifter when jumping between the lessons and #Xcode while using #VoiceOver. Most of this has been review, but I really want to get comfy with this language so I can be more effective at being an iOS #Accessibility Engineer. So far so good! #Blind #BlindCoding

  18. I'm finally sitting down and working my way through #100DaysOfSwift, and have passed checkpoint 5 and managed to get through Closures. My M3 Pro is making learning this much...um...Swifter when jumping between the lessons and #Xcode while using #VoiceOver. Most of this has been review, but I really want to get comfy with this language so I can be more effective at being an iOS #Accessibility Engineer. So far so good! #Blind #BlindCoding

  19. I'm finally sitting down and working my way through #100DaysOfSwift, and have passed checkpoint 5 and managed to get through Closures. My M3 Pro is making learning this much...um...Swifter when jumping between the lessons and #Xcode while using #VoiceOver. Most of this has been review, but I really want to get comfy with this language so I can be more effective at being an iOS #Accessibility Engineer. So far so good! #Blind #BlindCoding

  20. I'm finally sitting down and working my way through , and have passed checkpoint 5 and managed to get through Closures. My M3 Pro is making learning this much...um...Swifter when jumping between the lessons and while using . Most of this has been review, but I really want to get comfy with this language so I can be more effective at being an iOS Engineer. So far so good!

  21. I'm finally sitting down and working my way through #100DaysOfSwift, and have passed checkpoint 5 and managed to get through Closures. My M3 Pro is making learning this much...um...Swifter when jumping between the lessons and #Xcode while using #VoiceOver. Most of this has been review, but I really want to get comfy with this language so I can be more effective at being an iOS #Accessibility Engineer. So far so good! #Blind #BlindCoding

  22. I love learning new things every time I build a new website. Recently redid all the nav bars of my main sites by loding one file in via jQuery instead of stupidly copy pastaing the code into each page. Also wrote my own JS script that applies aria-current and a CSS class to the correct link based on the page that is loaded. It's just fun to noodle around with this all even if I may be designing quite a few years behind everyone else. Still better than react! :) #a11y #BlindCoding

  23. I love learning new things every time I build a new website. Recently redid all the nav bars of my main sites by loding one file in via jQuery instead of stupidly copy pastaing the code into each page. Also wrote my own JS script that applies aria-current and a CSS class to the correct link based on the page that is loaded. It's just fun to noodle around with this all even if I may be designing quite a few years behind everyone else. Still better than react! :) #a11y #BlindCoding

  24. I love learning new things every time I build a new website. Recently redid all the nav bars of my main sites by loding one file in via jQuery instead of stupidly copy pastaing the code into each page. Also wrote my own JS script that applies aria-current and a CSS class to the correct link based on the page that is loaded. It's just fun to noodle around with this all even if I may be designing quite a few years behind everyone else. Still better than react! :) #a11y #BlindCoding

  25. I love learning new things every time I build a new website. Recently redid all the nav bars of my main sites by loding one file in via jQuery instead of stupidly copy pastaing the code into each page. Also wrote my own JS script that applies aria-current and a CSS class to the correct link based on the page that is loaded. It's just fun to noodle around with this all even if I may be designing quite a few years behind everyone else. Still better than react! :)

  26. I love learning new things every time I build a new website. Recently redid all the nav bars of my main sites by loding one file in via jQuery instead of stupidly copy pastaing the code into each page. Also wrote my own JS script that applies aria-current and a CSS class to the correct link based on the page that is loaded. It's just fun to noodle around with this all even if I may be designing quite a few years behind everyone else. Still better than react! :) #a11y #BlindCoding

  27. @hpux735 a cloud editor can break the constraints of being on an iPad, e.g. Codespaces:

    dev.to/cubikca/using-github-co

    github.com/features/codespaces

    There’s a technical preview of CoPilot Voice that might help, since that works with VSCode, and that’s the IDE in Codespaces:

    githubnext.com/projects/copilo

  28. I had an #coding idea right as I got into bed, pulled out my laptop, checked out a new #git branch, researched, wrote out the code, tested, committed and merged on the first go, pushed the results up to my site, then realized it was 3am. Whoops. #BlindCoding #Flow

  29. I had an #coding idea right as I got into bed, pulled out my laptop, checked out a new #git branch, researched, wrote out the code, tested, committed and merged on the first go, pushed the results up to my site, then realized it was 3am. Whoops. #BlindCoding #Flow

  30. I had an #coding idea right as I got into bed, pulled out my laptop, checked out a new #git branch, researched, wrote out the code, tested, committed and merged on the first go, pushed the results up to my site, then realized it was 3am. Whoops. #BlindCoding #Flow

  31. I had an idea right as I got into bed, pulled out my laptop, checked out a new branch, researched, wrote out the code, tested, committed and merged on the first go, pushed the results up to my site, then realized it was 3am. Whoops.