5/ The real magic of MCP is when it deeply integrates into your actual coding flow. You can now ask your AI something like ‘wrap this in a feature flag’, it writes the code, it auto-creates or fetches the flag, and self-targets you into the flag for testing.
Seems rude to call Claude’s JavaScript garbage.
You don’t want Claude coming for you when sentience hits
Stop doomscrolling trade war takes and get building with Open Standards
blog.devcycle.com/open-standar...
Not sure that a trade war was on anyone's 2025 bingo card back in December 😅
Any use cases you’ve found that tend to work particularly well?
Cool, yeah I’m trying to approach these coding tools with the idea that I want to stay out of the code completely, and see how far it can go.
I’ll definitely check out bolt
Anyone tried replit yet and have any recommendations to get it out of error loops?
I was playing around with it and the google api and it couldn’t figure out a way past the error. For reference I’m trying to do as much as possible with just prompts.
But the problem isn’t really helpdesks, it’s making sure that the right people and processes are in place to make sure that gets answered right and actioned the first time
Go on
Oh yeah so that should be your first. It’s a PS set of games but came out with the PS4.
It’ll blow your mind if you like story driven games.
Not a PS5 game but have you played last of us?
An image of DevCycle’s interface showing off stale feature notifications
The team just launched Stale Feature Notifications into beta on Friday.
Really stoked about this functionality.
One of the biggest problems with feature flags is a build up of conditionals.
It’s our job to make it just as easy to remove a flag as it is to create them.
You picked the team’s overall favourite ❤️
Anyone here like to give design opinions?
Which badge style do you prefer? (Context on request)
Pretty much eh
Or when you think the fix to whatever the problem is, is always just around the corner.
Infinitely better feeling than the opposite, if you have support issues growing in lockstep with your usage
No-code A/B testing is a mirage.
Companies will sell you the dream of visual A/B testing where you can get impact with no engineering effort.
This is a lie.
If you want impact, experimentation should start with engineering and move outward at your org.
Product pricing is somehow all at once ubiquitous, dull, challenging and elusive.
As a startup you’re not meant to innovate on pricing strategies, but the decisions behind why other companies choose their pricing strategies is completely opaque.
Fun 😏
