tartieret

Joined 5 years ago

Karma

427

Submissions

Member since

Nov 24

CTO at Panevo (https://panevo.com)

https://www.linkedin.com/in/thomastartiere/

View on Hacker News

Recent submissions

Comment · 22 days ago

Yes, there is a page about Preparing (https://quakeimpact.ca/prepare/), but I agree that a list would be useful.

I have my own spreadsheet in which I keep track of what I have with expiration dates, so that I know when to renew, I was thinking of making this a reusable template

Comment · 22 days ago

Thanks for taking the time!

I prefer to avoid having commercial links and don't intend to make this a business, but I'll see if I can reduce the text. the challenge is trying to keep this a reference and explain things properly

Show HN: What a major earthquake does to Vancouver quakeimpact.ca

2 tartieret 22 days ago 5 comments

Comment · 2 months ago

having built two enterprise data platforms in python, I can't disagree more. for a startup, development velocity matters more than code performance especially for a CRUD app even at medium scale. Frameworks like Django simply enable you to do so much and so quickly. and you can reach world scale, that's what Instagram did!

Comment · 2 months ago

I have definitely noticed this in our organization as people use more AI tools. At first educating by providing feedback to the developers, then after a few repeat directly requesting that a PR is broken down if there is an obvious way to do it.

But the thing that really made the differences: 1) having a small github action that checks the size of a PR and leave a warning comment if it's large. Obviously some PR have to be large but then the developer has to justify 2) much better: getting early access to Github Stacked PR. we all like the experience and it solves a number of problems. without it even if you are disciplined and break down your work on several PRs, you end up having to deal with rebasing them one by one when the base moves. We modified Claude.md so that it tries to use it when it makes sense and now even AI generated changes result in stack of small PRs

I think it's worth investing in this as there are studies showing that review time is exponential with the size of PRs (or worse you are more likely to let defect go through on a large PRs). And AI agents are also better are reviewing smaller chunks.

I had personally several experiences of asking someone to break down a super large PR into smaller ones and found a defect in PR#2 which wasn't caught in the original AI driven PR review

Comment · 2 months ago

Over the last 6-9 months, I build an app to calculate the optimum jet lag management plan from a combination of flight. It tells you the optimum times for light exposure, sleeping, taking coffee...

It started with a naive "I know the tricks, let put them in an app" based on my own travel experience and quickly turned into a pretty nasty constrained optimization problem to optimize a cost function while keeping the schedule realist. So far I have been slowly releasing with friends and family, but I am pretty happy with the results as it can handle pretty complex combination of flights and layovers, compared to other similar apps.

If anyone wants to poke at it, I'd love to have some feedback! https://www.jetlagcoach.com

Comment · 4 months ago

After ~20 years of long-haul travel, I spent the last 9 months building Jetlag Coach, in parallel with my busy life (full time job toddler and pregnant wife!). You give it your chronotype and your actual itinerary (multi-leg and layovers included) and an optimization engine generates a personalized schedule for light, sleep timing, caffeine and melatonin to shift your circadian clock toward the destination time zone.

At core it turned out to be a complex optimization problem and a real challenge to tackle. I also put a lot of care in the UI/UX, while I usually focus more on backend work. It's working well, I am just finalizing the handling of some of the nastier edge cases