> if you need that level of documentation, trying to shoehorn it into package.json is just the wrong place for it. Soon enough your package.json looks like a graffiti wall.
So the right place is to make a graffiti out of another place, instead of in the place where people actually declare the dependencies?
I find it bizarre when people believe in one true way of doing things. I mean, you can declare your dependencies how you like, but if others do it differently, then they're clueless?
I would argue that the gain is more than "negligible" in some cases. I'm building an app involving storing and serving images and I'm surprised that for the same images with the same resolution/quality, WebP is often 3x-4x smaller than PNG, which translates to lower storage cost, faster serving time, and happier users. You made a good point that people with older devices wouldn't be able to use apps like mine. But for me, the gain is so significant that I might just accept that.
I'm working on Pictera [1], an AI product where users can upload their photos (like selfies) to create high-quality, hyper-realistic images of themselves in just about any style they want.
Originally, I built Pictera for myself to use because I couldn’t find any service that produced decent photos. Besides, I was very concerned that popular products in this space included broad terms allowing them to keep and use users' photos indefinitely for any purposes, including marketing [2]. But I've been enjoying working on the product so much that I've put way more time into polishing it and thought others would find it useful too.
Now, it's been a very long time since I see a mention of "Internet Explore 5". Kudos for highlighting the support for it but does it matter, who in the world are still using Internet Explorer 5?
Wish all browsers, at least the big ones, would do this by default. It would save regular users like us from fumbling around trying to figure out what works.
Great point on focusing on high-impact tests. I agree that LLMs risk giving a false sense of coverage. Maybe a smart strategy is generating boilerplate tests while we focus on custom edge cases.
Are there any browser extensions or tools that effectively prevent fingerprinting including canvas fingerprinting? Or is this one of those privacy battles we just have to accept as unwinnable?
Sounds like you're living the dream! I definitely agree that a few months of safety net doesn't feel "safe" at all and 1-2 years is more reasonable. One question, how did you initially start building that network of clients to reach a point where word of mouth sustains the business?
Thanks for sharing your journey, it's very inspiring. I'm curious, how did you find your first enterprise clients, and what strategies helped you secure long-term projects? Any advice for building that initial trust as a solo consultant?
I used to freelance and I can totally relate to the "feast or famine" cycle. Freelancing often sounds ideal—freedom, flexibility, and the chance to work on diverse projects. But the reality of inconsistent income, lack of benefits, and the need to constantly hustle for clients.
For those who have freelanced for a while, do you find it sustainable long-term, or is it more of a stepping stone toward building something more stable, like a product or SaaS? And how do you manage the stress of income unpredictability? Curious to hear from people who've made freelancing work on a larger scale.
Wait, you're a Captain, and you fear of taking off and landing? I have so many questions :). Also, as someone who is scared of taking off and landing, I'm even more scared now.
Very nice. Some are actually very useful. Suggestion: keep the sidebar on the left when inside an app, instead of requiring users to going back. Easier to explore the tools.
I'd recommend learning PHP if it helps with immediate job opportunities. PHP is still widely used in many places so that skill won't come to waste. However, long-term, learning a more versatile language like JavaScript or Python could open a few more doors, not just backend roles.
Heroku's PostgreSQL is still free. As for dynos, the lowest tier is $5/mo for multiple apps (not production traffic of course, maybe for MVP), with custom domain support.
So the right place is to make a graffiti out of another place, instead of in the place where people actually declare the dependencies?
I find it bizarre when people believe in one true way of doing things. I mean, you can declare your dependencies how you like, but if others do it differently, then they're clueless?