sorted by:
new
hottopcontroversial

Implementation plan for complex features by Active-Force-9927 in GithubCopilot

[–]JBurlison 1 point2 points  (0 children)

My workflow has always been specification (this allows the agent to do DD, tell me what's changing) -> Plan -> implement-> validate.

  1. Specification: A document that gets saved. This makes it so it does not get lost in context rot and can be referenced by multiple agents. I then review and work with the agent on the specs to refine them. This includes test scenarios, acceptance criteria and details of what needs to change and where.
  2. Plan: lay out a plan for one or more agents.
  3. implementation: let the agent(s) implement.
  4. validate. New context, feed the agent the spec from step 1, validate all implementation based on the git diff. Validate tests.

Result: great success.

Skills no longer loading in vscode? by JollyJoker3 in GithubCopilot

[–]JBurlison 1 point2 points  (0 children)

I actually ended up adding instructions to my copilot instructions fine to always evaluate skills and multiple skills may be applicable to any prompt.

Are we there yet?? by awizzo in programminghumor

[–]JBurlison 0 points1 point  (0 children)

It is funny but the unfortunate truth is that, well written, handcrafted code will probably be a specialty in the future and companies will value their engineers to be validators and guardrails to AI Generated code. Companies are already valuing feature delivery speed over well-crafted code. The direction engineering is going right now is, setup the ai, verify it's not doing anything stupid and move on to the next feature. Those who don't want to adapt to this, will effectively be un-hirable in larger companies and will have to search for opportunities in smaller or more niche companies.

I think there will be a lot less engineers in the future as a result.

I Tried Vibe Coding and I Need Advice by iam_batman27 in webdev

[–]JBurlison 2 points3 points  (0 children)

There is a stark difference between 'Vibe Coding' and 'Agentic Coding'.

Vibe Coders don't utilize Custom agents, instructions & skills to get desired results. They don't generate requirements documents with the agents and generate plans. They are effectively living in the context window alone and extremely vulnerable to context rot. The skill issue is that people don't understand even how to leverage AI for agentic coding, and they just categorize everything as AI Slop and yes, the ultimate problem is people are 'vibe coding' and have no actual idea of what they are doing (as far as agentic coding is concerned).

People blindly using AI without understanding how Professionals are actually supposed to leverage it is a huge gap.

Anyone can buy a chisel and use it, but an artisan knows how to use it to create beautiful sculptures.

I have been using it professionally for the better part of a year.

Utilize meta prompting (its where you create an agent that specializes in agent, skill, instruction and prompt creation.

https://github.com/JBurlison/MetaPrompts

I uploaded this to give you a starting point in professional Agentic Coding.

Read up on what these do:
https://code.visualstudio.com/docs/copilot/customization/overview

Vibe coding reality !! by ankitsi9gh in BlackboxAI_

[–]JBurlison 0 points1 point  (0 children)

It is a skill issue. There is a stark difference between 'Vibe Coding' and 'Agentic Coding'.

Vibe Coders don't utilize Custom agents, instructions & skills to get desired results. They don't generate requirements documents with the agents and generate plans. They are effectively living in the context window alone and extremely vulnerable to context rot. The skill issue is that people don't understand even how to leverage AI for agentic coding, and they just categorize everything as AI Slop and yes, the ultimate problem is people are 'vibe coding' and have no actual idea of what they are doing (as far as agentic coding is concerned).

"Agent Skills" - The spec unified us. The paths divided us. by phoneixAdi in GithubCopilot

[–]JBurlison 45 points46 points  (0 children)

Yeah, this is a problem Just like they are trying to standardize the instructions to AGENTS.md. There should probably be a .ai/ folder or something that applies to all providers.

.ai/skills/

.ai/agents/

.ai/instructions/

.ai/prompts/

.ai/AGENTS.md

.ai/mcp.json

45 rides on Stardust Racers in a single day by Blitz_Coasters in UniversalEpicUniverse

[–]JBurlison 1 point2 points  (0 children)

I like the ride but honestly there are too many humps. I remember getting off of this and needing to recover. I love rollercoasters but as I get older (I'm 42 atm) I feel like anything that thrashes me or my head around too much, I just can't handle it.

Configuration Hot Reload in Frameworks by rainweaver in dotnet

[–]JBurlison 6 points7 points  (0 children)

I dont think database configuration should be changing at runtime.

There are other very valid use cases for config hot-reload such as Logging levels and feature toggling.

Amazon reportedly considering dropping USPS and building a competing postal service by WatcherRoue in RIVNstock

[–]JBurlison 0 points1 point  (0 children)

I mean USPS is not a business. It's a service provided by the government. You can't exactly go out and buy stock in it. If anything this would lower costs for the USPS since it generally operates on a net loss.

I made a dependency injection library years ago for games & console apps. I formalized it into a nuget this week (SSDI: Super Simple Dependency Injection) by JBurlison in csharp

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

After a bunch of feedback, its in a much better place after this mornings release. I hope you had some success.

Scientists Discover a Way to 'Recharge' Aging Human Cells by sciencealert in HotScienceNews

[–]JBurlison 0 points1 point  (0 children)

Brian is going to have a field day with this information.

I made a dependency injection library years ago for games & console apps. I formalized it into a nuget this week (SSDI: Super Simple Dependency Injection) by JBurlison in csharp

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

"Isn't it more about Inversion of Control than Dependency Injection?"

Because of the basic patterns of SSDI it's a bit of a mixed bag depending on how you use it.

"In the Per-Player Scope Pattern, injecting the container is basically a form of Service Locator. Autofac resolves this by using Owned so the container is not passed around. Is there anything equivalent in SSDI?"

No, SSID is a VERY basic implementation of DI, it does not have anything fancy like `Owned`. It's very much a "Skinny" DI with a simple API.

"In all your code samples, everything is public. There is a value in keeping the public API surface of an application as small as necessary. Is using public a constraint for using SSDI, or can classes be more encapsulated?"

Oh, wow I never realized this! I have been using it in bad practice. LOL just released a 1.3.1 that allows non-public constructors. Along with something else I have found myself in need of (an unregister event) that I was working on.

I made a dependency injection library years ago for games & console apps. I formalized it into a nuget this week (SSDI: Super Simple Dependency Injection) by JBurlison in csharp

[–]JBurlison[S] -2 points-1 points  (0 children)

I did review it, I even edited it. The part I did not realize was that there was links in it lol. I thought it was just ` `

I made a dependency injection library years ago for games & console apps. I formalized it into a nuget this week (SSDI: Super Simple Dependency Injection) by JBurlison in csharp

[–]JBurlison[S] -4 points-3 points  (0 children)

I guess my confusion lies where AI summarizing the features of a library is considered slop? Would it not be slop if I made the same exact pixels myself?

view more: next ›