- 2 Posts
- 15 Comments
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
2·4 天前Early adopters will be rewarded by having better methodology by the time the tooling catches up.
Too busy trying to dunk on me than understand that you have some really helpful tools already.
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
2·4 天前This is why I say some people are going to lose their jobs to engineers using AI correctly, lol.
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
3·4 天前Well, I typed it with my fingers.
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
2·4 天前Incorrect, but okay.
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
8·4 天前While it’s possible to see gains in complex problems through brute force, learning more about prompt engineering is a powerful way to save time, money, tokens and frustration.
I see a lot of people saying, “I tried it and it didn’t work,” but have they read the guides or just jumped right in?
For example, if you haven’t read the claude code guide, you might have never setup mcp servers or taken advantage of slash commands.
Your CLAUDE.md might be trash, and maybe you’re using @file wrong and blowing tokens or biasing your context wrong.
LLMs context windows can only scale so far before you start seeing diminishing returns, especially if the model or tools is compacting it.
- Plan first, using planning modes to help you, decomposition the plan
- Have the model keep track of important context externally (like in markdown files with checkboxes) so the model can recover when the context gets fucked up
https://www.promptingguide.ai/
https://www.anthropic.com/engineering/claude-code-best-practices
There are community guides that take this even further, but these are some starting references I found very valuable.
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
4·4 天前If you’re not already messing with mcp tools that do browser orchestration, you might want to investigate that.
For example, if you setup puppeteer, you can have a natural conversation about the website you’re working on, and the agent can orchestrate your browser for you. The implication is that the agent can get into a feedback loop on its own to verify the feature you’re asking it to build.
I don’t want to make any assumptions about additional tooling, but this is a great one in this space https://www.agentql.com/
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
2·4 天前That’s a great methodology for a new adopter.
Curious if you read about it, or did it out of mistrust for the AI?
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
4·4 天前Great? Business is making money. I already explained we have human reviewed PRs on top of full test coverage and other validations.
We’re compliant on security policies at our organization, and we have no trouble maintaining what the current code we’re generating because it’s based on years of well defined patterns and best practices that we score internally across the entirety of engineering at our organization.
As more examples in the real world:
Aider has written 7% of its own code (outdated, now 70%) | aider https://aider.chat/2024/05/24/self-assembly.html
https://aider.chat/HISTORY.html
LibreChat is largely contributed to by Claude Code, it’s the current best open source ChatGPT client, and they’ve just been acquired by ClickHouse.
https://clickhouse.com/blog/clickhouse-acquires-librechat
https://github.com/danny-avila/LibreChat/commits/main/
Such suffering from the quality! So much worse than our legacy monolith!
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
3·4 天前We have human code review and our backlog has been well curated prior to AI. Strongly definitely acceptance criteria, good application architecture, unit tests with 100% coverage, are just a few ways we keep things on the rails.
I don’t see what the idea of paircoding has to do with this. Never did I claim I’m one shotting agents.
TurdBurgler@sh.itjust.worksto
News@lemmy.world•Illinois officials warn rental car companies that it is illegal for immigration agents to swap license plates
16·4 天前Enforced by the same police that helped ICE be violent towards peaceful protestors?
I once read ADHD described as “nearsightedness of the future” aka time blindness.
I think about that a lot.
TurdBurgler@sh.itjust.worksto
Programmer Humor@programming.dev•Programmers are no longer needed!
7·4 天前Your anecdote is not helpful without seeing the inputs, prompts and outputs. What you’re describing sounds like not using the correct model, providing good context or tools with a reasoning model that can intelligently populate context for you.
My own anecdotes:
In two years we have gone from copy/pasting 50-100 line patches out of ChatGPT, to having agent enabled IDEs help me greenfield full stack projects, or maintain existing ones.
Our product delivery has been accelerated while delivering the same quality standards verified by our internal best practices we’ve our codified with determistic checks in CI pipelines.
The power come from planning correctly. We’re in the realm of context engineering now, and learning to leverage the right models with the right tools in the right workflow.
Most novice users have the misconception that you can tell it to “bake a cake” and get the cake ypu had in your mind. The reality is that baking a cake can be broken down into a recipe with steps that can be validated. You as the human-in-the-loop can guide it to bake your vision, or design your agent in such a way that it can infer more information about the cake you desire.
I don’t place a power drill on the table and say “build a shelf,” expecting it to happen, but marketing of AI has people believing they can.
Instead, you give an intern a power drill with a step-by-step plan with all the components and on-the-job training available on demand.
If you’re already good at the SDLC, you are rewarded. Some programmers aren’t good a project management, and will find this transition difficult.
You won’t lose your job to AI, but you will lose your job to the human using AI correctly. This isn’t speculation either, we’re also seeing workforce reduction supplemented by Senior Developers leveraging AI.
TurdBurgler@sh.itjust.worksto
News@lemmy.world•US air travelers without REAL IDs will be charged a $45 fee
1·4 天前How to get a REAL ID and use it for travel, https://www.usa.gov/real-id
TurdBurgler@sh.itjust.worksto
Selfhosted@lemmy.world•Veronica Explains why she doesn't stream (from Netflix etc) #algorithmic_helplessness_sucksEnglish
8·6 天前This is why the seedbox SaaS market exists. Providing turn key hosted solutions, the only heavy lifting is the configuration which takes some reading to understand.
Check out the Servarr Wiki, Ombi, Syncthing as a starting point for media discovery and curration tooling.



It depends on the methodology. If you’re trying to do a direct port. You’re probably approaching it wrong.
What matters to the business most is data, your business objects and business logic make the business money.
If you focus on those parts and port portions at a time, you can substantially lower your tech debt and improve developer experiences, by generating greenfield code which you can verify, that follows modern best practices for your organization.
One of the main reasons many users are complaining about quality of code edited my agents comes down to the current naive tooling. Most using sloppy find/replace techniques with regex and user tools. As AI tooling improves, we are seeing agents given more IDE-like tools with intimate knowledge of your codebase using things like code indexing and ASTs. Look into Serena, for example.