This was a great read. Thanks to the author for the vulnerability.
In this thread and others, HN does a lot of talking about the fixed properties of these languages and frameworks.
Something I don’t see much is: choose the tool that you and your team are most familiar with.
It’s relatively easy to learn a new language, but it takes a long time to learn an ecosystem. Learning that ecosystem takes time away from focusing on your customer.
I recently started a new web app and tried to use Django because of the batteries-included framework “should” have been the right tool for the job.
But I haven’t used Django in 15 years and it was slow going. After a few weeks of slow going, I rewrote the whole thing in Typescript in a week. Not because of any general argument that TS is better, but because it’s the ecosystem I know well. Not by choice, but as a function of the jobs I’ve had.
I’d like to suggest that it’s okay to choose the tool you’re most familiar with, because you’ll move faster, write better code, and frankly web apps can be written in any of these languages.
Oh wow. I love the idea of DevLog. I’ve spent a lot of time helping engineering teams get better at regularly communicating what we’re doing, with context, that everyone in the company can understand. Have you shared this yet?
The indication for EoE is weekly, though I seem to be able to get away with every other week.
Dupixent is a subcutaneous auto-injector pen, so it’s the least-bad injection.
Injections definitely suck and everybody has to make their own trade-off assessment.
If you can’t figure out your triggers, and a lot of people can’t, it’s great that we have an effective therapy available now. It dramatically improved my life … once I got over injection anxiety
FYI for any other EoE folks: Dupixent is now indicated for EoE. It’s resolved my symptoms completely (both the ones I notice and the ones my gastroenterologist checks via scope). I don’t experience any side effects.
It’s an off-label use, but swallowed fluticasone is also effective for many people. Also has no to minimal side effects. I did that for many years before dupixent was available.
Exciting that you figured out your trigger. I collected a lot of data and made a lot of graphs, but never found anything conclusive.
Great article. Taking control of your health via the tools we have as technical professionals is awesome.
Here’s a guide on exploring 120 years of global weather measurements with Clickhouse. I enjoyed following this guide over a weekend. Also it gives you a sense of the dataset, even if you’re not interested in the clickhouse part.
https://clickhouse.com/docs/en/getting-started/example-datas...
Copia Automation | Sr Software Engineer, Head of Product | Remote + NYC | copia.io
Want to work on building DevOps tools for industrial automation? We’re building better code and ops tools for factories, warehouses, and anywhere that the physical world is automated.
Copia Automation | Sr Software Engineer, Staff Software Engineer, Head of Product | Remote + NYC | copia.io
Want to work on building DevOps tools for industrial automation? We’re building better code and ops tools for factories, warehouses, and anywhere that the physical world is automated.
In this thread and others, HN does a lot of talking about the fixed properties of these languages and frameworks.
Something I don’t see much is: choose the tool that you and your team are most familiar with.
It’s relatively easy to learn a new language, but it takes a long time to learn an ecosystem. Learning that ecosystem takes time away from focusing on your customer.
I recently started a new web app and tried to use Django because of the batteries-included framework “should” have been the right tool for the job.
But I haven’t used Django in 15 years and it was slow going. After a few weeks of slow going, I rewrote the whole thing in Typescript in a week. Not because of any general argument that TS is better, but because it’s the ecosystem I know well. Not by choice, but as a function of the jobs I’ve had.
I’d like to suggest that it’s okay to choose the tool you’re most familiar with, because you’ll move faster, write better code, and frankly web apps can be written in any of these languages.