“Jeremy did a great job for us. He was able to jump in on all projects we asked him to participate in, quickly surmounting the learning curve on each. He was the most well-balanced member of our team. I would hire him again in a second.”
About
Pragmatic, experienced software developer, building solutions on .NET Core
Activity
-
In our newest blog, Rachel Hutcherson discusses three ways #AzaraDRVS tools can be used to improve #Medicaid Redetermination rates and help mitigate…
In our newest blog, Rachel Hutcherson discusses three ways #AzaraDRVS tools can be used to improve #Medicaid Redetermination rates and help mitigate…
Liked by Jeremy Maddrey
-
It’s hard to know what to say other than simply… “Thank you.” Thank you to all of our associates, past and present, for the dedication you had to…
It’s hard to know what to say other than simply… “Thank you.” Thank you to all of our associates, past and present, for the dedication you had to…
Liked by Jeremy Maddrey
-
After more than eleven years leading and growing our family business to be a leader in pre-hospital emergency trauma products, and after assisting…
After more than eleven years leading and growing our family business to be a leader in pre-hospital emergency trauma products, and after assisting…
Liked by Jeremy Maddrey
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
Licenses & Certifications
Recommendations received
9 people have recommended Jeremy
Join now to viewMore activity by Jeremy
-
After 5 amazing years with Slalom I have decided to move on to another exciting opportunity with Abbott. A big thank you to Slalom and all the people…
After 5 amazing years with Slalom I have decided to move on to another exciting opportunity with Abbott. A big thank you to Slalom and all the people…
Liked by Jeremy Maddrey
-
Yours truly was interviewed in this month's Charlotte Magazine. Check it out! https://lnkd.in/ejM7AXn
Yours truly was interviewed in this month's Charlotte Magazine. Check it out! https://lnkd.in/ejM7AXn
Liked by Jeremy Maddrey
-
A joint industry statement on COVID-19 from Microsoft, Facebook, Google, LinkedIn, Reddit, Twitter and YouTube:
A joint industry statement on COVID-19 from Microsoft, Facebook, Google, LinkedIn, Reddit, Twitter and YouTube:
Liked by Jeremy Maddrey
-
New Vacancy: Research Manager – Impact and Evaluation The Research team at ARUK is fast paced, highly collaborative and committed to achieving…
New Vacancy: Research Manager – Impact and Evaluation The Research team at ARUK is fast paced, highly collaborative and committed to achieving…
Liked by Jeremy Maddrey
Other similar profiles
Explore more posts
-
John Craft
Let's chat about containerized software and why it's a total lifesaver when it comes to keeping those dinosaur apps and operating systems on life support. Believe it or not, but some folks out there are running ancient software: FoxPro databases, FileMaker, VB6, and possibly Windows XP (gasp!). Raise your hand 🙋♂️ if that’s you. Those setups worked well when they were originally built and they might still be chugging along, but they are about as compatible with modern systems as a floppy disk in a smartphone. That's where containers come in handy! They can act like time capsules for your software, wrapping up your legacy gems with all their weird dependencies and long-forgotten libraries. Obviously, moving away from those relics is ideal but sometimes that isn’t possible. Containers can buy you some time until the old tech can be retired.
2 Comments -
HealthEdge
Exclusive Webinar: Optimizing Retroactive Configuration Changes with HealthEdge Source™ Join Chief Strategy Officer Jared Lorinsky, and Director of Product Management Carl Anderson in a deep dive that demonstrates how your health plan can: -Track configuration-based changes -Streamline workflows -Increase payment accuracy Save your seat today: https://ow.ly/vqyG50RrhgG #PaymentAccountability #PaymentIntegrity #ClaimsConfiguration
-
Lakshmi Valluripalli
Why Code Reviews Aren’t Just a Checkbox, and How Code Generation Tools Can Help In fast-paced development environments, it’s easy to treat code reviews as just another task to check off. But in my experience, code reviews are essential for maintaining code quality, enforcing standards, and fostering team collaboration. They’re not just about catching bugs. Reviews improve code readability, consistency, and knowledge sharing. Rushing or skipping them often leads to technical debt and issues down the road. As teams scale and deadlines tighten, AI-powered code generation tools can help by automating repetitive tasks like code duplication checks or comment generation. But here’s the thing—AI tools don’t replace code reviews. AI can’t make judgment calls about: - Whether code aligns with business goals - How well it fits into the architecture - Whether there’s a better solution AI should assist, not replace, human judgment. Let AI handle the grunt work, but real code quality comes from thoughtful, human-driven reviews. Code reviews are opportunities for growth and quality—don’t treat them as a checkbox.
3 Comments -
Andrey Solovyev
Code quality is a kind of abstraction, a subjective judgment that, however, directly affects your budget for running software. It’s a clear analogy: if your contractor builds a low-quality structure, it’s you—the owner—who will deal with the consequences long after everyone else has moved on. You’ll pay for leaks, higher maintenance costs, and sometimes even renovations. Clear, right? Unsurprisingly, the same applies to software. If your code quality is impaired, it’s you—the owner—who will pay for expensive updates, fixes, and, occasionally, the need to redo large parts of your code. What does it mean for code to be impaired? In the picture below, there’s an artificial and toyish example: calculating a discount. Both sides do exactly the same thing. But the left side is bad (sometimes referred to as “spaghetti code”), while the right side is ok. Now, imagine you have a thousand lines like the left side—changing anything becomes nearly impossible without breaking something, while the right side is more manageable. If you make changes to the right side, you can do so one part at a time; it doesn’t require multiple changes for, say, adjusting the size of a student discount. How does it become possible for you to end up in a situation where a sane person would have to read the code? Well, there’s almost zero probability that the same people who wrote your code will be the ones maintaining it. The job market is active, and software engineers often change jobs within a couple of years. Sooner or later, you’ll find yourself as the owner of a codebase with a few new developers trying to figure out how everything works—and by the way, the only way to do that is to read the code, no magic there :) This is where the quality of the code starts to affect your budget. If the code you own is written in a way that makes it difficult for someone to understand just by reading it, you’ll constantly receive requests for extra budget approvals to redo various parts. Conversely, clear code allows your engineers to focus on implementing the new market features you’re asking for. One of the tech giants shared an interesting statistic: code is read approximately five times more frequently than it is written. The same tech giant has a policy every engineer must follow: "You write code not for yourself—‘I understand it, and that’s enough,’ not for the machine—‘It works properly, and that’s enough,’ but for other engineers who are going to read it. Therefore, your code must be clear and easily readable." It turns out that code quality—or code clarity—is something you should care about while the software is being developed. What’s a simple test? If you’re not a programmer but can understand the English in the code while keeping the logic in mind, it might be okay. However, it’s much better to have some technical expertise on your side when accepting code.
-
James Higginbotham
Recently reviewed an enterprise's API style guide. Found this nugget. FYI, style guides are like API documentation - they benefit from a great developer experience. - Standards must be clear and understandable. - Don't assume prior knowledge. Define concepts clearly. - Don't make people guess the intent. Provide examples.
1 Comment -
Adrian Ching
Will Devin AI replace developers? 😱 Maybe 🤷🏻♂️ To me personally, Devin is a development tool and not a replacement...YET 🌚 I am not denying that Devin can code really well if all the claims are accurate. Eventually, it may replace developers. But developers don’t code just to code. We build products ✅ We build solutions ✅ And these happen to be made of code. Can companies ditch all developers today and expect products to still get built and maintained to the same standard as an enterprise-level solution? Nope 🙅🏻♂️ The quality of a product refers to how well it solves user problems. And those gaps between code, user, and solution? That’s where good developers provide values 👨🏻💻✨
Explore collaborative articles
We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.
Explore More