Prabashwara Seneviratne (bash)

I always got the eslint directives wrong the first time 😆

Why not😄

This is what I have so far. It is all about tracking the effort that is put into tasks. Doing this has helped me be more consistent in the past.

Right now it's extremely primitive and buggy. But it's online and I can create an account for you if you like.

That's some interesting stuff! I didn't know about most of them so I had to do some googling😆. Would love to see what the end result is!

On my end, I have a strange obsession with effort tracking and I've built several apps for myself which I've abandoned after a while. I'm on the 5th one rn.

Hey Kacper! Welcome!
I'm probably in the same boat as you when it comes to abandoned side projects 😆
Are you working on anything right now?

Filtering | Sentry for JavaScript Learn more about how to configure your SDK to filter events reported to Sentry.

I just set up thirdPartyErrorFilterIntegration yesterday on Sentry. It seems to be a better fit for cutting out random noise.
docs.sentry.io/platforms/ja...

If the cookie is set on the server, then this kind of functionality could be implemented by checking the responses to see if the Set-Cookie header is set.

Would love to hear what you discover in the end. I would also suggest Astro for your consideration. Out of what I have seen so far, it is the one that I would mostly likely go with for a server side web app framework.

What frameworks have been less chaotic, based on your experience?

I would be more worried if your urgent group had 104 items and TODO had only 3.

This is one of those times when React will throw a rather cryptic "Maximum update depth exceeded." error.

The same applies to any application, the larger it gets the more complicated it becomes.

Using something like React Router can help when implementing multiple screens within a React SPA. If the web app consists mostly of static layouts, a web framework like Astro would be a better fit.

I personally learnt React by building a small app while reading the docs. I would recommend the same, even though it might be a bit challenging sometimes.
Feel free to hit me up with any #react questions.

Seeing your work in the wild is a great feeling!

Hey Brittany! Welcome!
I haven't been on Bluesky for too long so I'm still learning the ropes. But I try to chime in on conversations around #react.

I write a small blog around react and web app dev at www.frontendundefined.com . Maybe you might find it interesting.

Nope, you just need to pass the toggle which is actually dispatch to an event handler and it will toggle back and forth.

I thought of it a few years ago and it makes it much easier to work with boolean state. I haven't measured the performance of it but I haven't noticed any visible performance hits in all of the components I used it in.

I'm still surprised that I managed to do all that I did yesterday. Previously buying a new domain and setting up DNS, HTTPS, a reverse proxy and docker would have taken me days. Yesterday I managed to do it within 2 hours. #indiedev life does this to you I guess.
#buildinpublic

It only sets isDarkMode to true and doesn't set it to false afterwards. I often use useReducer for such toggles.

const [isDarkMode, toggleIsDarkMode] = useReducer(state => !state, false);

Started with a broken project. Coded the entire day and ended with the MVP frontend and backend hosted on a brand new domain. It was a long day. But I'm happy.
#buildinpublic

I think it shows when a lot of care is given to a project.

What was the thing BTW?

It's tough when you put your heart and soul into something and when people don't value it.

Yes, with a package, the interface or API between it and the consumer is the main contract. Any behavior exposed from it, even accidentally, will become the behavior that the consumers expect from it.

It mutates state within the reducer. 😁

Most of my monthly post end up getting sent late in the day after which a few people immediately unsubscribe. It really makes me question why I do this lol.

I have been this person so many times. Everyone else in the co working space is having a party and I’m sitting in the corner, writing and editing, since it’s the last working day of the month 😆

Reflections on managing state In this post, I reflect on my experience of using multiple state management libraries and I describe the best practices I found for managing state in React.

In the last few months, I tried several state management libraries for React. While going through them, I started to see state management itself in a different light. I wrote down my thoughts in my latest monthly post.

I think most people dislike it because it is not type safe and because it is very easy to make a mess with it.

Entire wars start because of programming language semantics.

Take your time. If you are not ready to post it, then you are not ready to post.

That said, I have learnt the hard way that getting other’s thoughts is better than later.

I hate to break it to you… but building a productivity tool for Indie hackers is a good idea 😆