“Don is a first-rate software engineer. He is able to distill a problem to its essence, utilize his broad technology knowledge to choose and leverage the right technology and frameworks, and deliver some of the best and most reliable solutions I've ever seen. To top it off, Don is an outstanding asset in a team environment. He collaborates and communicates well, respects and accommodates his teammates, and deals effectively with challenging personalities. I would welcome, and hope to have the pleasure of working with Don again in the future.”
About
I am a systems engineer with over 25 years of experience building and supporting software…
Activity
-
When Ashley and I were in our first house together, we covered the whole place in sticky notes (and I mean the whole place)… You wake up → sticky…
When Ashley and I were in our first house together, we covered the whole place in sticky notes (and I mean the whole place)… You wake up → sticky…
Liked by Don Keeting
-
A startup ran the best AI coding setup money can buy. 9 seconds later, their production DB and all backups, gone. This story made me stop and read…
A startup ran the best AI coding setup money can buy. 9 seconds later, their production DB and all backups, gone. This story made me stop and read…
Liked by Don Keeting
-
Fake AI engineers have one tell that gives them away every single time. Ask them about a system they built that failed. Not one that succeeded. One…
Fake AI engineers have one tell that gives them away every single time. Ask them about a system they built that failed. Not one that succeeded. One…
Liked by Don Keeting
Experience
-
-
-
-
-
-
-
-
-
-
-
Education
-
Southwest Baptist University
-
-
Activities and Societies: Symphonic Winds, Jazz Band, Brass Choir, Concert Choir
-
-
-
Licenses & Certifications
-
2022 DevArc Program Graduate
Oracle Cerner
Issued -
-
-
Volunteer Experience
-
Server
Feed the People
Poverty Alleviation
-
Volunteer
The Father's Club, Inc | 501(c)(3)
- Present 3 years 11 months
Children
Working with the Lee's Summit North chapter.
Honors & Awards
-
Media Authority - Top Performers for March 2017
TopRecommendedProfessional.com
TopRecommendedProfessional.com a website that accepts nominees from the top professionals worldwide is pleased to announce the selected top performers for March 2017.
TRP recognizes Donald Keeting as a top professional in media authority.
“The most important thing you can do to increase your perceived value, is to position yourself as an authority in your area of expertise.” - Donald Keeting, Media Authority
Languages
-
English
-
Recommendations received
1 person has recommended Don
Join now to viewMore activity by Don
-
One of the coolest parts about owning a business is that I get to employ our 14-year-old son. He's our Relationship and Social Media Coordinator…
One of the coolest parts about owning a business is that I get to employ our 14-year-old son. He's our Relationship and Social Media Coordinator…
Liked by Don Keeting
-
Coding tests are screening for the wrong thing. I'll say it plainly. If your interview process asks a senior engineer to write an algorithm by…
Coding tests are screening for the wrong thing. I'll say it plainly. If your interview process asks a senior engineer to write an algorithm by…
Liked by Don Keeting
-
A system that works under normal conditions is not enough. Real systems need to work under stress. That’s where assumptions break and behavior…
A system that works under normal conditions is not enough. Real systems need to work under stress. That’s where assumptions break and behavior…
Shared by Don Keeting
-
Retries are one of the easiest ways to hide a problem. They make failures look temporary. Until they amplify load and make things worse. What…
Retries are one of the easiest ways to hide a problem. They make failures look temporary. Until they amplify load and make things worse. What…
Shared by Don Keeting
-
Systems rarely fail at their strongest point. They fail at the edges. Integrations, dependencies, and assumptions about external behavior. That’s…
Systems rarely fail at their strongest point. They fail at the edges. Integrations, dependencies, and assumptions about external behavior. That’s…
Shared by Don Keeting
-
Most outages aren’t caused by one big failure. They’re caused by small issues compounding. A slow dependency. A retry loop. A timeout that wasn’t…
Most outages aren’t caused by one big failure. They’re caused by small issues compounding. A slow dependency. A retry loop. A timeout that wasn’t…
Shared by Don Keeting
-
The biggest trap in software engineering right now is thinking an AI subscription replaces a solid system architecture. It is actually doing the…
The biggest trap in software engineering right now is thinking an AI subscription replaces a solid system architecture. It is actually doing the…
Liked by Don Keeting
-
Debugging in production is not the same as debugging locally. Locally, everything is controlled. In production, you’re dealing with timing…
Debugging in production is not the same as debugging locally. Locally, everything is controlled. In production, you’re dealing with timing…
Shared by Don Keeting
-
Most systems become hard to support long before anyone notices. Complexity builds slowly through small decisions. Each one makes sense at the time.…
Most systems become hard to support long before anyone notices. Complexity builds slowly through small decisions. Each one makes sense at the time.…
Shared by Don Keeting
Other similar profiles
Explore more posts
-
David Tuite
GitLab's own product roadmap shows Internal Developer Portals as "planned but not funded" — pushed beyond 2025. The gap leaves GitLab organizations navigating hundreds of repositories without a unified software catalog or governance layer. Self-hosting Backstage to fill this gap requires 3-12 engineers and typically takes 6-12 months to reach production. Roadie delivers a production-ready portal in hours at roughly $22-24 per developer per month versus the $450K+ annual cost of a dedicated platform team. The platform includes: → Auto-discovery across hundreds of repos with regex-based filtering → 11 GitLab-specific scaffolder actions for project creation → CI/CD visibility and contextual linking to GitLab → Tech Insights for governance at scale → Broker architecture for self-managed GitLab instances Read the full technical guide: https://lnkd.in/dCVvmV3R
2 Comments -
Jens Neuse
Unpopular opinion: the monolith got one critical thing right that microservices broke. A coherent, unified API. With a monolith, you had one API surface. Consistent naming. Clear relationships between entities. One place to understand the whole system. Microservices gave us scalability and team autonomy. But the API surface fragmented. Every team names things differently. Relationships between services are implicit. The "unified API" becomes a duct-tape layer on top. GraphQL Federation was supposed to fix this. And at runtime, it does — queries span subgraphs seamlessly. But at design time? Each team still designs in isolation. The unified graph is an accident of composition, not an act of intentional design. Here's the mental model that changed how I think about this: Design like a monolith. Implement as microservices. Start with the unified API you want. Design it as if it were a single system. Then decompose the implementation across teams. You keep the monolith's coherence and the microservice's scalability. You just need tooling that supports designing the whole before splitting the parts. I wrote about this approach in detail on our blog. But what's your experience — has your team found a way to keep API coherence across microservices?
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content