• 0 Posts
  • 322 Comments
Joined 3 years ago
cake
Cake day: July 3rd, 2023

help-circle


  • Kind of related, but I spent about 5 weeks straight a couple months back working on our Playwright tests at work. Lots and lots of race conditions, many because of poor code since nobody knew the framework well, but many were just uncontrollable server side and network issues. I modified so much code and optimized it to the point that the entire pipeline was running in about half the original time, and I was getting successful consecutive pipeline runs. I found out that the test server is a VM with 1 CPU core and 8gb of RAM. Playwright by default will run all test files in parallel but each individual test in each file in serial, so we had about 10 tests trying to run frontend tests at the same time on that hardware. I think per Playwrights recommendations, it should be something like half as many cores as concurrent tests or similar, so we weren’t close.

    Anyway all of that text to say I was able to get that increased from 1 to 2 cores, and 8 to 16gb of RAM. It’s still getting hammered, and it’s still having issues, but it’s no longer my problem, so the company gets what they’re paying for.


  • I’ve gone being the smartest person in the room in my previous couple roles (mostly because I was the only person with any IT or platform knowledge, not because I’m some prodigy) to the bottom of the totem pole and well behind the intelligence of my current team since I changed careers.

    It’s wonderful having people around that are smarter than me that I can learn from and ask questions to. It’s hard being the idiot on a team when you’re trying to improve and care about your work. Working with idiots that don’t care or seemingly never improve is the worst. I’ve learned more over the past 8 months than I have since I started my professional career.

    I like the phrase, “Never be the smartest person in the room”. Sometimes it happens, but in most situations, there is someone else that is more knowledgeable about something than you, and that’s an opportunity to learn.



  • Sleep Theory - Bye Bye Bye by NSYNC.
    Bad Wolves - Zombie by The Cranberries.
    Daughtry - Separate Ways by Journey.
    5 Finger Death Punch - Bad Company by Bad Company.
    All that Remains - The Thunder Rolls by Garth Brooks.
    Disturbed - The Sound of Silence by Simon and Garfunkel.
    Disturbed - Land of Confusion by Genesis.
    Alien Ant Farm - Smooth Criminal by Michael Jackson.
    A Day To Remember - Since U Been Gone by Kelly Clarkson.
    Electric Callboy - Everytime We Touch by Cascada.
    Framing Handly - Lollipop by Lil Wayne.
    Our Last Night - Running Up That Hill by Kate Bush.

    There’s definitely more, but those are some that I’ve enjoyed, sorry no I females in the list though, except a collab on Separate Ways.


  • You’re liable for the murder that you ordered. This is a legal distinction where building something isn’t. Technically if you order AI to kill someone and it goes off and does it, you didn’t kill someone, you prompted it to. This is all theoretical as AI doesn’t have the ability outright kill someone, so this is all under the presumption that AI has a physical means of killing someone unattended.

    If this AI were more like a gun where you pointed it at someone and commanded it to shoot, then you killed someone use AI as a weapon.

    I will say there is nuance that can be debated between when AI use crosses from a supplemental tool to vibe coding. I don’t have a clear cut answer on that and don’t have the drive to go into it further, but I will concede that.


  • Those are all false equivalencies. All of those are tools to supplement a job. Using AI to vibe code an app is not a tool, it’s wait service, like the comic illustrates.

    If you auto generated an entire message, like prompting AI to write you an email, then no, you didn’t write a message. If you auto complete words that you intended to write, then you used tools to help write a message that you created.

    A hammer is a tool to build something. Vibe coding is like buying an IKEA piece of furniture and claiming you built it. You didn’t build anything, you assembled someone else’s build. If you had a magic hammer trained on other people’s work and you told it to build a chair, then no, you would not have built a chair.

    Computer software is again a tool to complete a job. If you do the engineering, design, and build the antenna, then that’s like programming, yes you designed an antenna. If you tell the software you want an antenna and it generates plans you didn’t design an antenna, you ordered plans for one.

    If you ask AI to kill someone, that’s like taking a hammer and killing someone. Yes, you used a tool to kill someone.

    It’s the complete generation of work and the claim that someone did it themselves that is what AI works are at their core. There is a small skill to prompting most effectively, but that’s not creating anything. It’s at most building an outline for something. Skilled developers can review code and make corrections, but they didn’t create anything.


  • I think there’s some difference in 3d printing. If you find a premade model online with written settings, then print it saying you made it, taking credit for the design, that’s what vibe coding is more like. It would be more apt to say you printed it. If you create a model via 3d modeling, cad, gdnt, etc, then that’s more like programming, and you can say you made it and that be true and honest.






  • I barely proof read anything I type on my phone, and my comment history is a testament to that. I deploy code or system changes most days, but I proof read the shit out of those on top of the QC they goes through. Any company worth anything will have a process for reviewing and approving anything being deployed, or probably destroyed for that matter.