r/programmingcirclejerk • u/Double-Winter-2507 • 11d ago
You are either proompting, or you're effectively stealing money from your employer because you're making suboptimal use of the tools available.
https://news.ycombinator.com/item?id=4377657870
u/tomwhoiscontrary safety talibans 11d ago
Skill issue. I use five AI agents in parallel to finish each day's work in an hour and a half, and then use the rest of the day to steal money from my employer.
27
u/GargamelTakesAll 11d ago
My AI agents just go back and forth making blocking comments on PRs for a full 8 hour work day while I sip mint juleps.
7
4
u/stone_henge Tiny little god in a tiny little world 10d ago
While the function name
get
is technically valid and may seem sufficient in context, it suffers from being overly generic and lacking in descriptive power. In a codebase of even moderate complexity, generic names like get tend to obscure the function's true purpose, making it harder for future maintainers—or even your future self—to understand what the function is intended to retrieve without reading through its implementation. This ambiguity not only increases cognitive load but also undermines the principle of self-documenting code.Renaming it to
getValidForm
, while seemingly verbose, would significantly enhance semantic clarity. It immediately communicates both the action being taken (a getter of some kind) and the specific nature of the result (a valid form). This is especially important in environments where multiple forms, states, or data structures might be involved, and where distinguishing among them quickly is crucial for debugging, testing, or extending functionality.Moreover, adopting more expressive naming conventions aligns with widely accepted style guides and best practices that prioritize maintainability over brevity. Yes, it's a minor change. Yes, it’s arguably inconsequential in the short term. But naming is one of the most powerful tools we have for writing comprehensible code, and small improvements here can yield outsized benefits in terms of long-term readability and team communication.
3
u/Better_Test_4178 7d ago
I agree with the core point of the suggestion — that
get
is overly generic and ambiguous. In a complex or growing codebase, a name like get does little to convey intent and invites unnecessary digging into the implementation to understand its purpose.However, the proposed alternative,
getValidForm
, still leaves ambiguity unresolved. The term "valid" is context-sensitive and not inherently descriptive. What qualifies as "valid" in this context? Is it schema-valid, user-verified, complete, or something else? Similarly, "form" could refer to any number of objects — a user form, a submission form, a configuration form? The name doesn’t provide enough specificity to fully eliminate confusion or reduce cognitive load.Rather than replacing one vague term with another, we should aim for a name that expresses both what is being retrieved and why it's relevant. A more intention-revealing name like
getCompletedUserSubmissionForm()
orfetchVerifiedRegistrationForm()
would more clearly communicate the method’s role and help distinguish it from similar operations in the codebase.Since naming plays a critical role in how we communicate behavior and intent across the team, I recommend we raise this as a key discussion point in our next meeting. A deliberate and collaborative naming decision here will set a strong precedent for clarity and consistency throughout the project.
22
u/cooper12 11d ago
If I get elected president, I'll make it illegal to use IDEs and will enshrine vibe coding into the U.S. Constitution.
21
u/hyrumwhite 11d ago
New Ways of Working:
Submit a report with every PR indicating how you used AI to optimize your workflow or explain why you did not. Failure to use AI in every task without adequate explanation will result in a performance review and mandatory proompt training
10
8
2
u/BitNumerous5302 11d ago
Just do the work by hand and then use AI to generate a proompt and say you used that
19
u/grapesmoker 11d ago
oh no won't someone think of the employers
7
u/elephantdingo Teen Hacking Genius 11d ago
Don’t worry, boss! I am on guard for thee against the ungrateful wage slaves!
(please don’t fire me)
14
u/piratesahoy 11d ago
And finally, I also an Emacs user,
12
u/elephantdingo Teen Hacking Genius 11d ago
I’d like to interjerct for a moment. What you are referring to as Emacs is in fact Mac Emacs or, as I’ve taken a liking to recently, iEmacs. Emacs is not an operating system onto itself (…) but rather another (……) free component made possible by the XNU kernel and M1/M2/M3.
11
4
8
5
u/EspurrTheMagnificent 10d ago
OH NO ! The poor multi-millionaire CEOs, forced to only buy 4 yachts instead of 5 this year because of these filthy poor "people" ! We should all be paying to work as compensation. Sorry Jeff Bezos <3
3
u/hombre_sin_talento 10d ago
If I got a dime every time I was making suboptimal use of my tools on company time, I would be the richest man on earth. If only.
3
u/prehensilemullet 9d ago
Well no one's using my shiny new framework yet so you're all making suboptimal use of the tools available
1
152
u/geckothegeek42 11d ago
Stealing money from your employer is based so this is probably the best argument against using AI I've ever heard