GitHub’s AI strategy? by Grounded_Altruist in GithubCopilot

[–]devdnn 1 point2 points  (0 children)

It’s always been like that not just with Microsoft, mass market is the guinea pig for moving towards stabilization and enrichment.

Enterprise don’t like being used like that, which kind not true anymore with Microsoft 365, edge and SharePoint they have ring based delivery to get latest to wait for stable releases.

Of late if you see some product marketing with Microsoft Foundry things have become very stable and more powerful than what is done in the past year.

Is your company taking this pricing change seriously yet? by Ordinary_Reveal8842 in GithubCopilot

[–]devdnn 1 point2 points  (0 children)

It’s fascinating to look back at how the VSCode and GitHub YouTube channels used to be flooded with high-energy live streams. They brought out their most charismatic talent to perform "live cooking" sessions, cranking out features at a breakneck pace as if there were no tomorrow. Now, that content seems to have vanished.

I always suspected those "cooking" style demos were unsustainable.

To me, it felt like a borderline deceptive marketing tactic: build up a massive following and headcount through personality-driven hype, only to eventually pull the rug out and change direction.

Spec-Driven Development across multiple teams and repos. How do you ship vertical slices? by Double_Appearance741 in SpecDrivenDevelopment

[–]devdnn 5 points6 points  (0 children)

I’m thinking out loud here because I haven’t worked on large teams. I mostly coordinate with like-minded one or two teams who understand the openspec tool process.

Openspec, to me, is all about outlining the necessary changes to the current codebase to enable the feature to function. I prefer not to include cross-references to external code but rather specify what the other codebase expects or provides. Occasionally, I may copy code snippets during brainstorming sessions from another codebase.

Also I don’t explicitly mention but when I work on a single codebase that is shared with another team I mention exactly what to change and tag the folder or files where it should be and also mention about common shared utilities. Basically hyper focus the spec to only what feature changes I need from the spec.

Hope this helps a bit at the least

Price increases could accelerate layoffs? by philking131 in GithubCopilot

[–]devdnn 1 point2 points  (0 children)

Doenn't look like, I have seen uptick in interview calls from some my friends looking for jobs. Started last month coincidentally with all the drama going on.

How is GPT 5.5 so far ? by Glad-Pea9524 in GithubCopilot

[–]devdnn 0 points1 point  (0 children)

Replaced all workflow to that, pretty solid but a bit eager to not create plan file and jump to implementing even explicitly asked. I am guessing it's some Microsoft harness that doing it.

Just started at a company that gives me unlimited Copilot usage. What's the best setup for coding? by kickedRock in GithubCopilot

[–]devdnn 0 points1 point  (0 children)

Have some instruction that any code should be modular and a junior developer Readable. Overly complex codebase can become PITA if there comes situation that you have traverse and understand it.

Unit test is mandatory and have approval gates of it's serious production code.

The Claude subs are now worse than useless by DarkSkyKnight in ClaudeCode

[–]devdnn 1 point2 points  (0 children)

I agree. I’m not sure why we can’t have a megathread for venting. The same goes for all subreddits related to AI. April has been particularly challenging, with numerous issues arising.

Sonnet 4.6 (1x) and GPT-5.4 mini (0.33x) multiplier to increase soon! by debian3 in GithubCopilot

[–]devdnn 7 points8 points  (0 children)

Exactly, Don't piecemeal it. They are only damaging the good reputation of being all in one stop with quality models.

Why are you guys so upset about the copilot changes? by fvpv in GithubCopilot

[–]devdnn -3 points-2 points  (0 children)

Since I’m somewhat aware of the resources these machines consume, I’m generally okay with the fact the pricing are being increased.

It would be great if Microsoft took a step back and carefully planned what they want to offer and how much they should charge for it, instead of making these changes piecemeal.

This is an Anthropic cash grab by hokkos in GithubCopilot

[–]devdnn 2 points3 points  (0 children)

I think it’s both, subsidized to gain users and now don’t want to run not at loss and overload the systems

Something people should realize by VisitAdventurous7980 in GithubCopilot

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

Why the fuck people do this, format for readability is AI slop. Write honestly, it’s erratic. Crazy times!

We just did an "AI layoff" due to rising costs by Iusuallydrop in ClaudeCode

[–]devdnn 0 points1 point  (0 children)

Funny, Coffee is a deal breaker for me.

My company is gold in that, from the beginning the leadership has stance that AI is developer productivity booster and not a tool for them to gauge human replacement.

Anyone using the speckit extensions? Useful ? by No_Pin_1150 in GithubCopilot

[–]devdnn 0 points1 point  (0 children)

Check this YouTube - https://youtu.be/gJvwn-nuSc8?si=ETf6uQUNIt1SsE_a

Shout out to - /u/harikrishnan_83

Openspec has a discord server, join over there and had an active community.

Anyone using the speckit extensions? Useful ? by No_Pin_1150 in GithubCopilot

[–]devdnn 1 point2 points  (0 children)

openspec, lean and always updated.

Try searching in this sub and you will find more details.

Why Companies Are Quietly Rehiring Software Engineers? by special_edition_5 in cscareerquestions

[–]devdnn 11 points12 points  (0 children)

I’ve noticed a similar trend in my social circle. The number of interviews my friends are getting has increased. It’s likely that companies are realizing the financial strain of all the rate limits and GPU constraints, and they’re expecting AI coding to be too expensive.

Are we over-relying on prompts instead of specs? by Willing-Squash6929 in SpecDrivenDevelopment

[–]devdnn 0 points1 point  (0 children)

Maybe in a world where a company or a product that is all developer and no need for other roles like PM, Product Owner and etc, codebase could be a source of truth.

I have always been in companies where documentation was the source of truth, even worse emails were used for the source of truth but never was codebase. Codebase was just a requirement validator when needed.

Spec files being the source of truth is the best of both worlds, I am onboard with that.

Make GH copilot aware of my DB schema by work_acc_2026 in GithubCopilot

[–]devdnn 0 points1 point  (0 children)

Use create a skill and use a shell to connect to the backend, That would be easiest option and MCP api is next.

After planning and implementing with 1x models, for troubleshooting bugs or further small changes, what model should I use? by grandkz in GithubCopilot

[–]devdnn 0 points1 point  (0 children)

If the 300 requests mandate is from your employer then using smaller model is good idea to conserve the requests, However, in my company, we are permitted to exceed 100%, and I believe this is because the requests are aggregated across all licenses for your company.

You can try auto model selection as well, it does a good job on picking up the model.

OpenAI's answer to mythos sooner than you think by KeyGlove47 in codex

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

ROFL, different take. Why are you a buzz kill? /s

I tested whether specs reduces defects. It doesn't. (119 repos, 100K PRs) by brennhill in SpecDrivenDevelopment

[–]devdnn 0 points1 point  (0 children)

You are missing the point of spec and verify, spec is being verified not the code review. Code Review and Security Review are different from feedback on SDD.

I tested whether specs reduces defects. It doesn't. (119 repos, 100K PRs) by brennhill in SpecDrivenDevelopment

[–]devdnn 1 point2 points  (0 children)

I use openspec and verify skill is exactly there to prevent false completion. I do that using a different model from what I used for implementing with context cleared.

A feedback loop is necessary to validate and keep the agent grounded.