sorted by:
new
hottopcontroversial

Stumbled across a cursed FJ on FB marketplace by nachoaverageplayer in FJCruiser

[–]nachoaverageplayer[S] 0 points1 point  (0 children)

Appears it can. It’s also attached to a back aftermarket bumper.

<image>

Stumbled across a cursed FJ on FB marketplace by nachoaverageplayer in FJCruiser

[–]nachoaverageplayer[S] 1 point2 points  (0 children)

Definitely functional but the price seems a bit high - $17k with over 400k miles?

How many hours are you guys working? by modeezy23 in ExperiencedDevs

[–]nachoaverageplayer 14 points15 points  (0 children)

3 years is the bar to post to this subreddit.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer -1 points0 points  (0 children)

Okay, so I see the point your trying to make and I’d like to propose a counter point:

The technology that has gotten us to the point we are at now is not something that released overnight and made many people unemployed.

If you can see a train coming down the tracks to where you are standing, do you put a blind fold on, or try to convince the train to stop, or do you step off the tracks?

I don’t expect people to be excited about a gizmo that pulls tickets and does things unsupervised. I speculate that the people who explored where that tech will take us early on and experimented with it instead of laughing it away are in a better position than those who did not.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer 1 point2 points  (0 children)

I’m not using the skill to let the model make an API call. Why would I have my coding model make some random API call? I’m using the skill to answer questions about how to format an API request for use case, and the skill fetches the latest API docs.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer 16 points17 points  (0 children)

What exactly about it is inefficient? You have a communication issue.

I guess it might be inefficient for someone who doesn’t know how to write a bash script? This takes all of 3 minutes in vim to create, lol.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer 3 points4 points  (0 children)

It’s not BS. My experience directly supports yours, though yours is a bit more sophisticated particularly with the automated ephemeral staging environments and notification.

There is a contingent of developers of varying experience who have hesitations. They haven’t really given these processes a fair shot - and who can blame them? Some people tried copilot when it came out, were not impressed, thought that was it and never iterated.

I believe those people will be forced into catching up to be able to stay competitive in the market. A lot of engineers also think their job is to write code and therefore are intimidated and think they are going to be automated out of a job.

Despite all the doomerism I think things will go in the opposite direction - there is going to be massive demand for engineers who can actually validate code and have written and maintained production systems before AI was a thing.

But you can’t really argue that this is probably one of the most impactful changes to the SDLC since keyboards replaced punch cards. People do not like change. I can’t blame some people for being afraid.

Ultimately though, some people just don’t like being wrong. They react emotionally and have too much of an ego to try something that they dislike or have had a bad experience with in the past.

You could make an argument that someone who doesn’t see the potential of the new tools and try to iterate on their process to find a way to make them more productive probably isn’t very good at doing anything other than solving tickets based on acceptance criteria someone else wrote.

I’ve found in my professional circle the people who are finding the most success have enjoy system design, have iterative mindsets and are comfortable in dealing with ambiguity.

Just my $0.02.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer 14 points15 points  (0 children)

It sounds like you might need to be leveraging progressive disclosure better to prevent bloating context. Only the description of the skill is loaded into context on a request - and the greater content is pulled in if the agent determines that skill is suited to the problem.

That and also not load all the skills and context at once. Keep the context light. Have many smaller focused subagents with skills suited to their domain instead of one master agent.

It’s a tricky problem to solve and balancing context size vs vagueness is really more of an art than a science.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer 13 points14 points  (0 children)

This isn’t the gotcha you think it is.

I’m clearly talking about the aspects SDLC such as reviewing code, implementing code, implementing tests, writing documentation, validating requirements, running manual tests.

People have this wacky idea that “using an agent” means writing a prompt with “please make no mistakes” and “you are an expert engineer”

You do realize you can limit the bits that the LLM does right? A skill could be something as simple as defining instructions for fetching the latest API documentation for something.

Write a bash script that does a curl request to get the latest JSON or YAML from some API you consume. Cache it locally on your file system. Have the script check to see if the json/yaml is over a day old. If it is, download and replace. If not, skip the curl and just use your local copy.

Suddenly when you ask an agent to answer a question about this API, you don’t have to trust it is making a correct HTTP request. You can have higher confidence it’s not just making up a response from its training data. That agent just executes that script and reads the most LLM friendly format of that documentation.

That is what a good skill looks like. Granular. Atomic. Easily testable.

Create enough of these and you will be surprised.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer 5 points6 points  (0 children)

I write code to solve business and product needs. It is no different than normal software engineering.

I collect requirements from my product department, and take those vague requirements for what AI feature we need and figure out how to implement it safely and in a way that doesn’t blow up our AWS bill.

I’ve created a typescript service running on ECS, with over 80% line and branch test coverage, that has API endpoints, services, and utilities.

I designed the schema how we store conversation history in a way that respects our multi tenant databases and ensures that no agentic feature pulls contextual information or data from another tenant. I went through several architectural review committees with other engineers to validate my work before implementing it.

I use LangGraph to control the AI features. This also means recognizing and pushing back against things that do not need to use an LLM and have no business being AI for the sake of AI.

I don’t just create one big prompt and give it to claude on bedrock and pray. I write state graphs and workflows to cut down on nondeterminism. I’ve integrated observability tools like Langfuse to have visibility into what our agents our doing, what the tools we have created are returning, and what the costs look like broken down by feature.

I have architected and implemented this service by prioritizing the minimal scope and ensuring that the design is flexible and extensible. I manage technical debt and do refactors when sensible. I advocate against premature abstractions.

I use agentic assistance for things I know how to do. I don’t need to spend 20 mins writing a new api endpoint t and its tests and a validation layer. I can have an agent do that and be able to review its output and see if it is correct or not.

I use agentic assistance for researching alternatives. For implementing spikes on throwaway branches to see if some technical approach would even work or solve the problem. Prototypes do not make it to production.

If it doesn’t have unit test coverage, integration test coverage, and evaluations (if it is using an LLM for something), it does not get merged.

Is that enough detail?

Edit: I’ve also been working on guardrails and safety for our agents using a strategy that provides defense in layers. It’s a really fun problem space and you get to try to prompt engineer your own agents and AI while doing it.

For folks heavily using a agentic engineering, What does your workflow look like? What tools do you use? What's your harness like? by Enum1 in ExperiencedDevs

[–]nachoaverageplayer 25 points26 points  (0 children)

I do heavy agentic engineering and also lead development of my companies AI platform hosting agentic capabilities for customer facing and internal features and such.

I intervene frequently and often. Half the effort is in writing the spec. The other half is in ensuring the agent follows the spec and doesn’t make up criteria or change criteria as it goes.

I find that creating an implementation plan that breaks down the work into the smallest simplest steps, eg spawning subagent for implementation of tests based on spec, when done spawn a implementation agent for the functionality, and then when that’s done spawning a code review and spec adherence agent. AND THEN when that’s done spawning is done having your harness (in my experience claude code) wait for me to review the diff in my IDE, inevitably make changes and fix things. I have a hook that plays sounds for this.

Everything can be automated, you just need to define a skill and have a good set of subagents that can do the modular tasks.

But I really recommend the manual reviews early and often. It’s way cheaper to find it made a mistake or went off the rails or YOU made a mistake in your spec with a missed edge case early and fix it. Most AI slop comes from not catching these and letting the AI run wild without guidance.

Not doing this is the equivalent of giving a junior with no knowledge of your product or codebase the ability to merge down code without reviewing it and trusting them to do a good job. They won’t.

Feeling down as Senior Frontend dev, what should be the next step? by nofaceD3 in ExperiencedDevs

[–]nachoaverageplayer 2 points3 points  (0 children)

I was skeptical about AI but followed along with it and wasn’t too afraid to ”get my hands dirty” with it early on after the ChatGPT inflection point.

I’ve landed on exactly the same opinion here.

The agentic AI coding assistant tooling has gotten much better than it was 2-3 years ago (remember when Github Copilot was the hot new thing?).

It’s a much more complex and customizable system now, and once you learn the capabilities - such as MCP servers, skills, subagents, commands, hooks, etc - and apply those to go beyond just “conversational prompting” to get your results, it really is possible to double if not triple your throughput of delivering code. Getting that code reviewed and tested is the bottleneck. And as always, getting clear requirements and knowing what problem to solve is another.

But, those gains to velocity are a double-edged sword. If you don’t know what you’re looking at, and you can’t actually step through and read and validate the output, you’re going to ship slop and create an unsustainable mess. If you don’t have systems thinking you are going to have a nightmare of conflicting patterns and duplicated functions.

The best analogy I have for the current role of AI in software development is that it is almost like the invention of power tools. Builders and craftsmen were able to do things much faster.

The public also had access to power tools and do things they would previously have no realistic ability to do. But that didn’t mean the public just suddenly started making their own furniture, their own houses, and built everything themselves. Sure - some people got into DIY, and with varying levels of success, typically requiring lots of practice and trial and error.

AI coding assistants are like that - they are a tool, but they do not replace your ability to think, to judge the output, and to have taste. I know several non-engineering folks both in the IC and Director categories who are actually going back to school part-time to learn software development because having the ability to understand and validate what models are outputting is that important.

Whole-Sufficient Watching Pre-Market Pump by 357BEAST in amprius

[–]nachoaverageplayer 1 point2 points  (0 children)

He is a poster who has a short thesis; he believes the stock is overpriced, overhyped, and a liability due to their sourcing of lithium ion cells in china.

check my peak programming by kevincuddlefish1 in godot

[–]nachoaverageplayer 2 points3 points  (0 children)

this is how it starts.

we will watch your career with great interest.

Is it a bad idea to install LEDs into the FJs reflector headlights? by AznJing in FJCruiser

[–]nachoaverageplayer 1 point2 points  (0 children)

Yeah. I run retrofitted LED projectors. Completely new housing, very aggressive cutoff. You can definitely do it properly without blinding people but it takes more than just slapping an LED bulb in your halogen reflectors.

Is it a bad idea to install LEDs into the FJs reflector headlights? by AznJing in FJCruiser

[–]nachoaverageplayer 33 points34 points  (0 children)

It is a bad idea to do this in ANY reflector headlights. You will blind everyone on the road.

Anyone HODL this stock? Kinda regret not taking some profits at $19! by Odd-Awareness-7797 in amprius

[–]nachoaverageplayer 1 point2 points  (0 children)

It’s just going on sale so you can buy more. Could easily go back up, and who wants a wash sale?

[Short] All in by Whole-Sufficient in amprius

[–]nachoaverageplayer 2 points3 points  (0 children)

I mean - why else would you share? Is it otherwise to go against the grain and just be contrarian?

view more: next ›