Hackolade

The best compliments are from happy users

@GergelyOrosz What's your take on OCI?

Interesting thing I'm learning about Google, while doing my deepdive on them: Feels like there is no other company where there is *so much* aversion to build on the company's own cloud solution (GCP) as there is at Google. Most greenfield projects still don't choose GCP...

I am with Will on this. Kind of how since everyone has an amazing camera in our phones - those of us paying attention realize that making a movie worth watching takes more than having good lenses. And the video you or I take are not that good vs pros x.com/boujeehacker/s…

The positive thing about AI tooling going mainstream and setting expectations high (e.g. "anyone can build software with AI") is that a large group will learn what us devs know already: Creating good software is hard and it's hard to explain to outsiders in a way they understand

One of the most important concepts in Goldratt's "Throughput Accounting" is that inventory (something you've built or spent time on) that has not been released into the customer's hands) is a financial liability. It's money spent with no balancing revenue. Every bit of software that sits idle waiting for someone to work on it is a financial liability—money lost. Opportunity cost is a big part of that. You're paying to write non-revenue-producing software while at the same time losing the money you could have made had it been released earlier—a 2x hit. Of course, delayed feedback ultimately leads to either building the wrong thing or massively expensive rewrites. More money lost. Lots of it. A long backlog that people have put effort into creating and maintaining is inventory—more money lost. Every minute waiting for QA or a DBA decision is money lost. That 10x programmer creating work that's waiting to be handled by the next person in line—money lost. The list is endless. You want to be more profitable? Don't "manage" these delays and dependencies, eliminate them..

@allenholub I have not seen it work. It usually ends up being some sort of water-scrum-fall. How can an organization be agile if it keeps doing summer budget exercises with line-item details for the following year, 18 months ahead? The only way is to provide capacity and trust the teams.

I'm curious if anybody's witnessed a whole-org "Agile Transformation" that actually worked. I know of exactly one case (ANZ Bank, which was fraught but had committed C-level support, and the big snake-oil consultancies were shunned). My personal experience is that the only generally effective way to change an organization is incrementally, focusing on solving one problem at a time. This is, of course, just Gall's Law applied to organizational systems. I find that when you do that, culture follows. What is your experience?

Who’s the Bigger Villain? Data Debt vs. Technical Debt @hackolade #DevOps #SoftwareDeveloper thenewstack.io/whos-the-bigge…

Proactively addressing data management reduces debt and enhances scalability. @hackolade #DevOps #SoftwareDeveloper thenewstack.io/whos-the-bigge…

Reduce your data debt. Chart the present, then design the future of your data. #datamodeling

Next JSON Office hour's topic is: "JSON Relational Data Modeling" with a special guest: Pascal from Hackolade! Sign up here: bit.ly/3BwI0cd 8 October 2024, 03:00 PM UTC Don't miss this free event if you work with JSON! #Oracle @Hackolade #JSON #Datamodeling

8/ The psychological edge isn’t about outsmarting others; it’s about mastering yourself. Our greatest obstacles are often internal—the fear of failure, the pull of instant gratification, the comfort of conformity. When you can consistently overcome these internal barriers, you position yourself ahead of those who can’t. In a world where many succumb to their base instincts, understanding and conquering your own psychology gives you an advantage that’s both rare and enduring.

5/ Thinking unconventionally is where magic happens. Most stick to the beaten path, clinging to comfort and familiarity. But the real breakthroughs? They come when you dare to ask the questions no one else is asking. The road less traveled isn’t just for the bold—it’s for those who want to make real, lasting impact. Innovators don’t just follow trends—they set them.

2/Why is psychological strength the ultimate competitive edge? Because it’s what most people are missing. Human nature fights against it. Our instincts push us toward comfort, validation, and quick wins. Mastering these inner battles puts you leagues ahead of those who follow the path of least resistance.

@allenholub It is even worse to keep inventory (of developed code) on the shelves instead of shipping it to add value for users. If it is ready, release/deploy it.

In Lean thinking, "inventory" (things that you've spent money on but can't sell) is a liability. Your entire backlog is inventory, as is every piece of work that's blocked, waiting for somebody else to do something. Just sayin'.

@allenholub @AdrianHofman @WoodyZuill The only time I have asked for an "order of magnitude" estimate has been if I fear a misunderstanding on the solution. Maybe someone imagined a quick win while someone else is over-engineering a solution.

@allenholub @AdrianHofman @WoodyZuill I'll paraphrase in my own words... If you need something done, and you trust your team, then execution will take what it will take. Spending time to come up with estimates is a waste of time since estimates will be wrong anyway and will not affect execution.

What exactly do you think the "no estimates philosophy" is? I have a feeling that it's not what you think. For one thing, it's not a philosophy. @WoodyZuill coined the hashtag with a tweet that said that his team had just finished a major project without using estimates, along with a call to discuss that. There is no specific approach, or technique, or rules--only the observation that they're not needed in real projects, as proved by the fact that they were not needed in real projects. Actual companies work this way--hardly philosophical. So the question becomes, how can you move away from estimates in your context? There are many different answers to that question.

@mileswnash @Dynobase is a great tool built by a fantastic team. Also take a look at @hackolade.

One thing is for sure: we keep having more code out there that needs to be maintained. Keep coding, keep learning as an engineer, because there will be an even bigger need for experienced engineers. Often to clean up the existing mess in place: x.com/kageiit/status…

My first manager at Uber started a GitHub page back at the time with resources to become a more proficient developer - ones he personally found helpful (he did not have a CS degree). I realized he is *still* updating it, 7 years later! A neat list: github.com/charlax/profes…

Presenting at conferences is fun, but Developer Relations is about enabling customers to use your technology to solve their problems. If you spend more time talking than listening you won't know what those problems are.