Doesn't change anything about opus 4.7 being an absolute buffon. Even going back to opus 4.6 doesn't feel like the magical period maybe 3-4 weeks ago. Gonna go back to openAI
Meetings aren't even the worst resource wasters. Wrong initiatives, features, apps/platforms/services are. They capture future resources in form of maintenance and complexity with them.
Agreed, and this is where I think some more nuanced and conscious use of tech debt can be used when applicable.
It might be OK to place some bets on an initiative or feature, but if we all understand we're placing a bet, this is an area to load up on debt and really minimize the investment. This also requires an org that is mature about cutting the feature if the bet doesn't materialize, and if the market signal is generated will reinvest in paying down the debt. And also has the mega-danger territory of a weak market signal, where it's not clear if there is market signal or not, so the company doubles down into the weak signal.
Also these bets shouldn't be done in isolation in my view, well executed product and market discovery should also provide lots of relevant context on the ROI.
Totally agreed! I think good orgs that run well have a good feedback process and ownership between the individual teams. In my experience, the closer they work together, the more visible the impact is on ROI.
The less context everybody has, the higher the risk that an initiative goes sideways and doesn't fully match the intent.
And yeah, cutting features and offloading debt is important. I love that part when starting an engagement! It's a bit of work to check critical execution paths and how customers actually use a product, but it's a good excercise for everybody to see the relationship between revenue and code.
This all sounds easy and in reality it's not the hardest, but for some reason no one is doing it.
I do tech dd, exit readiness and post merger integration in tech companies and this is my daily bread. The biggest lever I have: connecting initiatives to ROI/bottom line impact. It's incredible how blind product/software teams run. So much to do but most of it won't make any money and just feels productive. Connecting activities and work directly towards revenue is very important.
If your company runs well: won't hurt you much that you're not doing this. Otherwise this will be your end. And that really hurts because you lose the economical impact of the product and the jobs.
Thanks for the feedback, I'll do that! I think different screens and system settings affect this a lot, on all the devices I've looked at the site on I felt it was quite comfortable to read, not to discount your experience, I'll keep that in mind for the future as well.
This website is absolutely horrible to use. We adhere to UX standards for a reason. That is familiarity so people don't have to think about how to use things. This website feels weird and I dropped out before I could read what it's about (there's also a reason that the landing page tells you what problem is being solved).
How do you use it? I explored building on this as a platform but ditched it because only crypto nerds seem to use it and fiat is used all around anyway.
