1,602 karma · joined November 8, 2012
https://thomasvilhena.com
> "engineers had identified DNS resolution of the DynamoDB API endpoint for US-EAST-1 as the likely root cause"
Interestingly, we found matching errors in our own logs:
> System.Net.WebException
> The remote name could not be resolved: 'dynamodb.us-east-1.amazonaws.com'
Occurrences were recorded on:
- 2025-04-30
- 2025-05-29
- 2025-06-17
- Yesterday
We had logged this as a low-priority bug since previous incidents only affected our AWS testing environments (and never our production env which is on Azure). At the time, we assumed it was some CI/CD glitch.
It now seems that the underlying cause was this DNS issue all along, and only yesterday did it start impacting systems outside of AWS.
Where it blurs things: data model != UX strategy != business model, and success isn't only about a novel model, execution and distribution still matter greatly.
My takeaway: read "data model" here as "core conceptual model", and ask whether your product has a clear center that lets new features inherit context instead of becoming one-offs.
Stablecoin issuers earn yield from holding U.S. Treasuries, which sustains their business model. Meanwhile, people in distressed economies get practical access to a digital dollar, often cheaper and faster than navigating restrictive exchange rules or paying steep conversion fees at money-changers. That’s meaningful when local currencies are unstable or losing value.
Of course, not all stablecoin issuers are trustworthy, and some governments under economic distress may ban or limit these instruments. But when the setup works, both sides benefit.
Nope. Machines are soulless automations. LLMs are algebra at scale, there’s no solid evidence to suggest otherwise.
The capacity LLMs have to mimic human reasoning should not be mistaken for actual human reasoning (which, to be fair, we don’t even fully understand).
PS: I’m considering a definition of “soul” that includes anything spiritual, emotional, or conscious.
PPS: I’m open (and eager) to change my view based on solid evidence :)
Can you share more about your strategy for "massive refactoring" with Gemini?
Like the steps in general for processing your codebase, and even your main goals for the refactoring.
> My feeling about legacy projects hasn’t changed – I still hate them (...) Instead of feeling resigned, we saw it as a place to ask questions and learn.
I see that you advocate embracing the opportunity to work on legacy projects, so I say even if you dislike legacy projects, try to avoid phrasing it so strongly. It might influence other devs in your team to develop a negative mindset toward them.
Crypto can replace some banking functions, such as payments, electronic transfers, and lending/borrowing.
One could argue that crypto eliminates the need for traditional checking accounts since you have full control over your funds with private keys. However, this doesn’t account for the legal safeguards and protections that banks provide.
> Am I going to get a mortgage in BTC?
I don’t recall seeing mortgage services in crypto yet. However, there are borrowing platforms like AAVE, primarily used for leveraging crypto investments or speculation. These platforms are decentralized, with strict collateral requirements, typically limiting borrowing to 80% of your collateral.
> If narrow banking, why give them my btc at all instead of holding myself?
Not sure I fully understand your question, but typically, when you lend your crypto to a service, you’re seeking to earn a yield in exchange for the risk of lending your assets.
> Does that even work on blockchain?
Theoretically, yes. You could create a narrow bank using crypto, but you’d need a decentralized mechanism to verify the bank’s holdings. This could involve creating an oracle (ex: Chainlink) service to confirm asset reserves.
> How do you do fractional reserve lending with a deflationary and one of one asset?
Instead of using deflationary assets like BTC, fractional reserve lending could rely on stablecoins, which are better suited for such systems. That said, not all stablecoins are equally reliable.
- https://thomasvilhena.com/2019/11/quantum-computing-for-prog...
Mentoring - As you build your network, you'll naturally find opportunities for informal mentorship. This could be someone with a solid career who has already navigated the tough paths and can help you tackle challenges while also offering guidance for your journey.
There have been many times in my career when I felt stuck. By having regular conversations, listening to others, and sharing work experiences, I gained a broader perspective and have always been able to found ways to move forward.
Argentina tried doing that, resulting in 100% inflation per month.
I'm finding Google Flights more reliable these days.
The few defending Scrum are doing so based on positive experiences with great teams and strong leadership.
In my view, high-performance teams don’t just appear by "hiring good people and letting them do their thing." Good people naturally communicate, take initiative, prioritize, estimate, provide updates, and mentor less experienced team members. In other words, they often follow a pseudo-process or even suggest routines that resemble a formal process, if one is not already in place.
Alignment, communication, transparency, and prioritization are key to achieving results. Processes should be designed to support these, providing space for creativity and autonomy, including review and constant improvement of the process itself.
That’s no easy feat and often oversimplifies the challenge of building competent teams. I think it’s achievable if you have a large budget to hire only senior/experienced devs and a mature hiring process/team. Plus, if your company has strong tech branding, it becomes easier to attract top talent too.
But if you’re at a startup with limited funding and possibly no branding at all, you’ll likely face this situation:
- Hire inexperienced but honest, motivated people with the potential to grow, and invest in mentoring them.
We have a simple cloud infrastructure. Last year, we moved all our legacy apps to a Docker-based deployment (we were already using Docker for newer stuff). Nothing fancy—just basic Dockerfile and docker-compose.yml.
Advantages:
- Easy to manage: we keep a repo of docker-compose.yml files for each environment.
- Simple commands: most of the time, it’s just "docker-compose pull" and "docker-compose up."
- Our CI pipeline builds images after each commit, runs automated tests, and deploys to staging for QA to run manual tests.
- Very stable: we deploy the same images that were tested in staging. Our deployment success rate and production uptime improved significantly after the switch—even though stability wasn’t a big issue before!
- Common knowledge: everyone on our team is familiar with Docker, and it speeds up onboarding for new hires.
The dunning krugger effect is widely regarded as the polar opposite of it:
- "If the Dunning-Kruger effect is being overconfident in one's knowledge or performance, its polar opposite is imposter syndrome or the feeling that one is undeserving of success. People who have imposter syndrome are plagued by self-doubts and constantly feel like frauds who will be unmasked any second." [1]
- "This is the opposite to the Dunning-Kruger effect. The Imposter Syndrome is a cognitive bias where someone is unable to acknowledge their own competence. Even when they may have multiple successes they struggle to attribute their success to internal factors." [2]
- "The opposite of the Peter Principle and Dunning-Kruger effect is the imposter syndrome. This is when smart, capable people underestimate their (...)" [3]
[1] https://www.psychologytoday.com/intl/basics/dunning-kruger-e....
[2] https://www.leedsforlearning.co.uk/Pages/Download/28541a2c-3....
[3] https://www.forbes.com/sites/jackkelly/2022/07/12/what-the-p...
Dunning–Kruger effect
I'm the technical co-founder. Under me, we have three squads. Two of them are led by managers who were promoted internally from individual contributor roles. These managers still do some hands-on coding occasionally when needed, but they primarily focus on delegating tasks to their teams as much as possible. The third squad has a manager without coding responsibilities, whom we hired to test a new squad structure. It's been going really well—his squad is performing excellently, and I've been able to delegate some cross-functional tasks that used to fall on me, like collaborating with the sales team when clients have technical requirements for renewing their accounts or documenting releases and bug fixes to share within the company.
So in terms of the technology area of our company, our lower-level managers are performing considerably well. We’re implementing frameworks and routines that are really helping to advance our company’s managerial maturity. We’re also working to apply these practices to other, less structured areas, so your proposal could be very timely.
We concluded that they were high-level managers with little hands-on experience, accustomed to having large teams to execute their plans. They were often slow to recognize their lack of progress, or didn’t recognize it at all, and frequently spoke about the need for more "strategic" actions when what we really needed was to focus on executing key priorities.
So I related to PG's post.
[1] https://thomasvilhena.com/2024/06/easy-wins-for-generative-a...
- Pigeon racing
- Cannon shooting
- Life saving
Among other interesting entries.
[1] https://en.wikipedia.org/wiki/Category:Discontinued_sports_a...