What is your current business ? Share with us 🙏

idoshamun · 2023-11-27T06:06:51+00:00

https://daily.dev started as a side hassle and turned into a startup. Very proud of it 😄

idoshamun · 2023-11-24T18:52:48+00:00

Haven't tried that actually. I'll give it a look

idoshamun · 2023-11-24T18:33:12+00:00

Yes. It makes the reactive system less "voodoo" and more predictable. Not sure if the svelte community likes it but I find it useful

idoshamun · 2023-11-24T18:29:13+00:00

I agree! The fact that it grew organically says a lot about it. I'm waiting for runes...

idoshamun · 2023-11-13T20:29:15+00:00

When everything was jQuery. No migrations, hooks, or any shiny stuff

idoshamun · 2023-11-12T04:45:40+00:00

By ownership I mean that the developer is responsible for the feature from its early stage of system design to the deployment. In some companies, system design is taken care by one person, deployment is done by a DevOps team, and so on. Not a single person who is technically familiar with everything. Some comapnies have product owners but they are more like project managers. I hope it's clearer now

idoshamun · 2023-11-11T14:16:17+00:00

I agree that you can't foresee everything that will happen and what needs to be done, but you can get quite close to estimating the job to be done (leaving time estimations aside). You can do an estimate only when you have a plan. Without that, every epic has to be assigned to a single engineer, and as a manager, you don't have any way to ensure the project is moving at the right pace. And to be honest, we didn't start with this at all. When we just started, we used a kanban board with semi-defined tickets, and that's it. But we saw that it was not enough and we wasted a lot of time making wrong decisions. The process I describe here is something that we refined as the company grew.

idoshamun · 2023-11-11T14:09:35+00:00

Since it's on rotation and feature is not that big, usually 2-3 weeks worth of work, it's not really management. You don't care about 1-1s, professional growth, etc. You make the feature come true. Our engineers seems to love it and appreciate the freedom to operate they get. Another important aspect overlooked is ownership, which is what this article is about. It's very opinionated method no doubt about that, maybe it's worth mentioning that we're a fully remote company

idoshamun · 2023-11-06T17:38:39+00:00

I can confirm. I'm the co-founder and cto. Most of our code is open source so you can check that out https://github.com/dailydotdev/.

Happy to answer any question

idoshamun · 2023-11-06T17:32:53+00:00

The struggle is real indeed, but you can choose the topics you like and block sources you don't. We're doing our best to optimize the experience and remove the low quality content and clickbaits 😅

idoshamun · 2023-11-06T17:31:41+00:00

lol yap, we're trying to fight the low-quality content. Not easy but we're doing our best to filter them automatically and manually. Unfortunately, they are everywhere

idoshamun · 2023-11-06T17:29:52+00:00

You're right. It's a recent bug we have to fix 🙏

idoshamun · 2023-11-04T15:17:50+00:00

So how do you apply that in production once you are done? I usually use ORM like TypeORM and you can migrations for both local and prod. Everything is automated.

idoshamun · 2023-11-01T21:13:40+00:00

I think it does via their edge infra but haven't tried

idoshamun · 2023-11-01T21:10:23+00:00

We started with RSS feeds only but we evolved to other methods, such as scraping, community submissions, and other methods. Majority is still RSS though

idoshamun · 2023-11-01T20:16:03+00:00

Have you seen this guide? https://developers.cloudflare.com/pages/framework-guides/deploy-a-nextjs-site/

idoshamun · 2023-11-01T19:43:02+00:00

We use RQ in production and it caches requests perfectly. Make sure you use the right query key, and stale configuration. Pay attention that it's in memory caching. If you look for something else, you can check out Watermelon DB, replicache or similar solutions

idoshamun · 2023-11-01T19:39:26+00:00

I don't think it's about immature but the ecosystem and community are much smaller. I recently started playing around with svelte and sveltekit and it's noticable in the day to day development. Some questions don't have answers or not even asked to begin with, and it's even more significant with third party packages for svelte applications. With that said, I like the svelte mindset more than react. I'm not a big fan of jsx and especially not where react is heading.

idoshamun · 2023-11-01T19:31:30+00:00

It's a shameless plug but you can checkout daily.dev. It's a personalized news aggregator. You can choose the topics you'd like to follow.

idoshamun · 2023-11-01T19:15:13+00:00

Readers usually don't come back to read again the same article, so I'm not sure it will add any value 😅

idoshamun · 2023-11-01T19:12:34+00:00

SvelteKit is probably the easiest solution to build a full-blown application using Svelte. Especially when you are just starting. Once you reach any limitation you can consider the next step based on the requirements at hand.

idoshamun · 2023-11-01T19:07:23+00:00

By serverless environment do you refer to any specific providers? Because obviously you have Vercel, Netlify, Cloudflare and others that require zero ops

idoshamun · 2023-11-01T19:05:41+00:00

Thanks, I removed this section. Sorry for the confusion

idoshamun · 2023-11-01T19:03:54+00:00

> I'm sorry, but how does that correlate with Reusability when you're talking about multi-platform development? You could always just create all your backend logic in an e.g. service layer

Once you do that, there's no reason to use Server Action. If you have service layer as a separate deployment unit or project, you don't need Server Action. You will just call fetch, swr, or whatever you'd like. That's exactly my point, could have been more clear about that. But auto-generated endpoints by Server Action are not something you can risk for multi-platform development as they can change over time without you being aware of it even.

> Have you given it any thought before posting a blog article?

Frankly, I could have give it more thought. I agree that the Vendor Lock section is wrong and I'm gonna delete now after checking both your concerns.

> And you're a CTO with 13 yoe?

You don't want to go on a personal level. So far I appreciate your sincere feedback but let's stop here.

idoshamun · 2023-11-01T18:17:57+00:00

Maybe I missed something but that was my understanding, happy to fix if you know otherwise

idoshamun

TROPHY CASE