No, we have SRE at home... SRE at home:
-
wrote on last edited by [email protected]
A landscape image of a (metaphorical) dog show. On the left, there is a server-rack labeled "Dev", and on the right another rack labeled "Prod". Programmers are running the course between the two on all fours (reminiscent of a dog) which consists of three hoops and a teeter-totter; there are also arrows on the floor. In the foreground, a manager with a clipboard has a speech bubble admonishing them "Another bug? Let's add another hoop."
-
A landscape image of a (metaphorical) dog show. On the left, there is a server-rack labeled "Dev", and on the right another rack labeled "Prod". Programmers are running the course between the two on all fours (reminiscent of a dog) which consists of three hoops and a teeter-totter; there are also arrows on the floor. In the foreground, a manager with a clipboard has a speech bubble admonishing them "Another bug? Let's add another hoop."
Ignoring the AI stuff, I don't even get the joke.
-
Ignoring the AI stuff, I don't even get the joke.
I'm guessing they aren't happy that QA and their SRE is putting in automated tools to prevent them from causing crashes in prod with their AI slop code.
-
I'm guessing they aren't happy that QA and their SRE is putting in automated tools to prevent them from causing crashes in prod with their AI slop code.
mOvE fAsT aNd BrEaK tHiNgS
-
I'm guessing they aren't happy that QA and their SRE is putting in automated tools to prevent them from causing crashes in prod with their AI slop code.
wrote on last edited by [email protected]The number of new devs who complain about having to write a unit test is too damn high
Don't get me started on Medium and Large tests
Edit: see below for examples
-
I'm guessing they aren't happy that QA and their SRE is putting in automated tools to prevent them from causing crashes in prod with their AI slop code.
Kind of the reverse... more lamenting the loss of QA and SRE roles in favor of mechanical (AI) code reviewers and non-technical persons rubber-stamping an increasingly deep pipeline that change requests must traverse.
-
The number of new devs who complain about having to write a unit test is too damn high
Don't get me started on Medium and Large tests
Edit: see below for examples
lol... if they had a job that was ONLY writing unit tests, I would take it!
-
The number of new devs who complain about having to write a unit test is too damn high
Don't get me started on Medium and Large tests
Edit: see below for examples
Personally I don't like unit tests. I'd rather have debug asserts and larger scope tests.
But using unit tests as debugging is near too
-
A landscape image of a (metaphorical) dog show. On the left, there is a server-rack labeled "Dev", and on the right another rack labeled "Prod". Programmers are running the course between the two on all fours (reminiscent of a dog) which consists of three hoops and a teeter-totter; there are also arrows on the floor. In the foreground, a manager with a clipboard has a speech bubble admonishing them "Another bug? Let's add another hoop."
More AI sludge clogging up the internet, yum yum
-
A landscape image of a (metaphorical) dog show. On the left, there is a server-rack labeled "Dev", and on the right another rack labeled "Prod". Programmers are running the course between the two on all fours (reminiscent of a dog) which consists of three hoops and a teeter-totter; there are also arrows on the floor. In the foreground, a manager with a clipboard has a speech bubble admonishing them "Another bug? Let's add another hoop."
I can draw programmer comedy at a relatively high speed, at no greater cost of water, power, etc., than I'm already using to live.
Speaking of which, I probably should draw some of my ideas...
-
The number of new devs who complain about having to write a unit test is too damn high
Don't get me started on Medium and Large tests
Edit: see below for examples
wrote on last edited by [email protected]The number of new devs who complain about having to write a unit test is too damn high
- Or writing integration tests
- Or passing CI
- Or following repo conventions
- Or following standards
- Or adhering to domain guardrails
- Or in adding monitoring
- Or in not logging everything as
info - Or in actually documenting features
- Or in receiving critical PR review
- Or in addition input validation
- Or in not trusting the client
...etc
Honestly most devs.... Kinda suck at their job. This is becoming more evident to me every year
-
The number of new devs who complain about having to write a unit test is too damn high
- Or writing integration tests
- Or passing CI
- Or following repo conventions
- Or following standards
- Or adhering to domain guardrails
- Or in adding monitoring
- Or in not logging everything as
info - Or in actually documenting features
- Or in receiving critical PR review
- Or in addition input validation
- Or in not trusting the client
...etc
Honestly most devs.... Kinda suck at their job. This is becoming more evident to me every year
most devs⦠Kinda suck at their job
Also they like to make memes about how it's the rest of the world that's doing best practices, software testing, teaching, and interviewing all wrong
-
most devs⦠Kinda suck at their job
Also they like to make memes about how it's the rest of the world that's doing best practices, software testing, teaching, and interviewing all wrong
wrote on last edited by [email protected]Also about how JavaScript is stupid because it didn't stop them from subtracting a user date input value from an empty object (which caused them to break their website (also what's TypeScript?))
-
A landscape image of a (metaphorical) dog show. On the left, there is a server-rack labeled "Dev", and on the right another rack labeled "Prod". Programmers are running the course between the two on all fours (reminiscent of a dog) which consists of three hoops and a teeter-totter; there are also arrows on the floor. In the foreground, a manager with a clipboard has a speech bubble admonishing them "Another bug? Let's add another hoop."
Screw this LLM!
-
Screw this LLM!
This is probably a diffusion model. LLMs don't create images.
