“ Over the course of the last several years, I’ve known Jeff to be a solid programmer and DBA. Working within the confines of a start-up, Jeff had no issues digging into core problems and resolving them. In addition, as the company began to grow, Jeff implemented a mentoring program for interns and new hires that quickly brought them up to speed on the core product offering and how they interacted with each other. I’ve work with Jeff on database upgrades and migrations from host to host using tools like slony and the built-in replication for Postgresql. Jeff is a methodical and detail oriented individual and is fantastic at recognizing ‘big-picture’ conversations and not getting too hung-up on minute details that don’t pertain to the overall project. As a DBA, I’ve seen him fight fires when needed to and help keep those fires extinguished through code/query optimization. Again, Jeff is able to see the bigger picture of a problem and isolate (or at the very least locate) the source of the problem and resolve. The one thing that sticks out specifically from Jeff is his willingness to share knowledge. I’ve never observed an individual better suited at sharing knowledge across a range of topics and (even better) to engage in the conversation without sounding like a ‘know-it-all’. Jeff’s ability to invite others into the conversation stands out by ensuring that an individual’s experience and alternate views are at least understood before any final decision is made. ”
Activity
-
I’m excited to share that I’ve accepted a position as a Software Engineering Intern at IStream Financial Services! I’m incredibly grateful to Joseph…
I’m excited to share that I’ve accepted a position as a Software Engineering Intern at IStream Financial Services! I’m incredibly grateful to Joseph…
Liked by Jeff Amiel
-
With gratitude and respect, iStream honors all who have served. We thank you for your service. We’d especially like to recognize Jeff Amiel, a…
With gratitude and respect, iStream honors all who have served. We thank you for your service. We’d especially like to recognize Jeff Amiel, a…
Liked by Jeff Amiel
-
So upsetting: last night, Beth Am in Los Altos Hills (our congregation) was swatted with a hoax bomb threat. No one was hurt, but it's still a…
So upsetting: last night, Beth Am in Los Altos Hills (our congregation) was swatted with a hoax bomb threat. No one was hurt, but it's still a…
Liked by Jeff Amiel
Experience
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Education
Projects
-
Postgres Open Conference Speaker
See projectTalk titled "Row-Estimation Revelation and the Monolithic Query Syndrome"
-
PGEast Conference Speaker
See projectTalk titled "Database audit trail in heterogeneous and sensitive environments"
Recommendations received
1 person has recommended Jeff
Join now to viewMore activity by Jeff
Explore more posts
-
Sylvain Aubé
Most teams are using AI wrong. They’re obsessed with prompts. Anthropic just showed the real play: → one CLAUDE.md file → with rules, memory, and lessons → turning AI into an operator — not an assistant Their system is simple and brutal: Plan first. Verify before done. Document everything. Feed lessons back. Meanwhile, most companies? Still using AI like a stateless intern. CLAUDE.md isn’t a hack. It’s a warning. AI won’t replace you. Teams with systems will. 🙏 🙏 🙏
-
Ademola Alaba Malomo
Most developers think a successful payment API response means the money has moved. It usually doesn’t. A 200 OK just means the request was accepted. The actual movement of money depends on the payment rail behind the transaction, and every rail behaves differently. 📝 Cards authorize instantly but settle later. 📝 ACH might take days. 📝 Real-time rails settle in seconds. 📝 Cross-border transfers can pass through multiple intermediaries. If you don’t understand the rail your payment runs on, it becomes easy to misread transaction states, retry incorrectly, or show users the wrong status. I just published a new guide for developers that breaks this down: “What Are Payment Rails? A Guide for Developers.” In the article I cover: • What payment rails actually are • How money moves from initiation to settlement • Why a successful API call doesn’t always mean a successful transfer • Push vs pull rails and how they affect system design • How to handle rails properly in APIs, webhooks, and ledgers If you build fintech products, payment systems, or anything that moves money, this is one of those concepts that makes a lot of confusing behavior suddenly make sense. Link in comment 👇
1 Comment
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content