The best compliments are from happy users

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/status/19…

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..

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

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

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.

@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/1767595…

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/professio…

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.

The Agile Manifesto says we "build projects around *motivated* individuals." ❤️ Want to know the 2 main reasons why Scrum and Agile transitions fail: 🤷‍♀️ 1. The individuals on the team are not motivated 😞 2. The individuals want to work in silos, not as a team 👯 The bigger problem? Many in the Agile community can't come to grips with the fact that some people are unmotivated, nor can they come to grips with what to do with those people. 🤦‍♀️ I once suggested on LinkedIn that destructive, lazy, unmotivated and deleterious employees should be let go, and the blowback was amazing. 💣 "You should do everything humanly possible before you let an employee go" was a common response. Of course, when I asked if they'd share their salary to keep the unmotivated employee motivated, the virtual signalling of 'doing everything' quickly came to an end. 💰 💰 💰 So what happens when you keep unmotivated and deleterious team members around? What happens when you keep people on the team who are lazy and don't do their work? Here's the reality: you have to manage them. 🤦‍♀️ ✅ You have to assign people who can't self-manage JIRA tickets. ✅ You have to track the work of unmotivated people. ✅ You have to give people who can't self-manage assignments. And you know what else? All of this ends up spilling over to the rest of the team. In the end, everyone gets managed. No organization hires a person to manage just one individual on a team. Everyone gets managed once a manager comes on the scene. If you want to be Agile, and you want Scrum to work, respect what the Agile Manifesto and the Scrum Guide says. Developers are expected to be motivated and self-managing. If you think Scrum will work, or an Agile transition will take hold with a group of unmotivated individuals who are unwilling to manage themselves, you are setting yourself up for some significant disappointment.

If you want to build a winning team it does not matter who is at fault when things don't go right. There is only one person responsible for failure and if you are a true leader then that person is you. Winners own the result no matter what.

People who always think big problems have simple answers are unlikely to deliver solutions that scale without breaking.

At @hackolade , we have since quite some time articulated our vision for treating "Metadata" as "Code" (hackolade.com/metadata-as-co…). This was not a coincidence: if data modeling is going to be effective and efficient in an #agile tech environment, we will need to make sure that it is *always* up to date, and we will need to make sure that the models accurately represent the conversation between #datamodelers, #developers, #devops, subject matter experts (#sme's) and #governance staff. The "#InfinityLoop" will become real, also for #datamodeling. This is ONLY going to be possible if *all* the stakeholders are always looking at the same source of truth. And precisely that implies that we will need to co-locate and collaborate on data models, in and around the same #GIT-based repository. The entire workgroup of stakeholders will use #GIT to collaborate and version their artifacts - and this is precisely what we enable with Hackolade Studio. We have made #GIT simple to use, for everyone. Of course, that means that we need to show you how. Hence, we have launched a new course on our #eLearning platform: community.hackolade.com/slid… will teach you, based on real world scenarios, how to go about this new concept. We hope you will enjoy it, and use these skills to even beter reconcile business and IT through a shared understanding of the context and meaning of data.

When you are developing or modernising a #datamodeling practice inside a large organisation, you will quickly find that the consistency and understandability of the data models - across a wide variety of different #sql, #nosql and other file based (#json, #openapi, #avro, #parquet, etc) data structures - is absolutely key. Without it, there is no way you can expain the significance of these models to your #subjectmatterexperts, #governance, #developer and/or #devops stakeholders. That's why the @hackolade Studio has some great functionalities to help with this: 1. you can implement #namingconventions across your data models, so that all terms are consistently used across systems 2. you can implement #modelverification across the data models, checking the data models against a number of different rules. Both these functionalities are super cool and interesting, and we have just released new #community #tutorials to help you understand them better: see * this tutorial (community.hackolade.com/slid…) for the Naming Conventions * this tutorial (community.hackolade.com/slid…) for the Model Verification functionality. We hope this will prove to be useful for you, and recommend that you try it out - for free - from hackolade.com/download.html ...