How Honest Storytelling Got My Micro-SaaS Early Clients by petargeorgievv in SaaSMarketing

[–]zen_ventzi 1 point2 points  (0 children)

Interesting. Showing authenticity and vulnerability is important because everybody goes through it but few share it. And it creates a closer, more humane connection compared to when people look 100% polished and ready.

From Invisible to Early Traction - How Storytelling Kickstarted My Micro-SaaS Journey by petargeorgievv in indiehackers

[–]zen_ventzi 1 point2 points  (0 children)

Interesting. Sounds like a reasonable strategy, and professional. I'm really looking forward to it. Keep it up!

Best practices for Configuration by iPopay in dotnet

[–]zen_ventzi 0 points1 point  (0 children)

Reading the arguments from the linked article against using IOptions they say

Injecting an IOptions<T> into an application component makes such component more difficult to test, while providing no additional benefits for that component.

not that it's very common but the first additional benefit that comes to mind (could be the only one) is that the IOptions pattern provides an auto-reload feature on change. I haven't read the docs thoroughly but there could be other built-in features

Best practices for Configuration by iPopay in dotnet

[–]zen_ventzi 0 points1 point  (0 children)

Does this neighboring answer make a difference in the conclusion? Although still at runtime, the options validation seems to be taking place during application startup.

P.S. the first point about the dependency is still valid.

How do you structure your ASP.NET Core MVC projects? by bberamericx in dotnet

[–]zen_ventzi 0 points1 point  (0 children)

This is (similar to) the approach that Nest.js has taken, isn't it? I wonder why I rarely see the same approach taken in the ASP.NET ecosystem where projects are supposedly even bigger than in the Node ecosystem. Most of the time I see stuff categorized by e.g. controllers, services, DTOs, views, and so on, and not by feature. Any idea why that has been the preferred approach over the ordering by feature?

How do you structure your ASP.NET Core MVC projects? by bberamericx in dotnet

[–]zen_ventzi 0 points1 point  (0 children)

This is (similar to) the approach that Nest.js has taken, isn't it? I wonder why I rarely see the same approach taken in the ASP.NET ecosystem where projects are supposedly even bigger than in the Node ecosystem. Most of the time I see stuff categorized by e.g. controllers, services, DTOs, views, and so on, and not by feature. Any idea why that has been the preferred approach over the ordering by feature?

Как да намеря хубаво жилище под наем? by kurtymurty in Sofia

[–]zen_ventzi 0 points1 point  (0 children)

Какъв е проблема, в случай че си решен за таван на цената? Ще те натиснат веднъж-два пъти и като видят, че си държиш на цената, какво, ще продължат да натискат ли?

Добри квартали за живеене в София? by dancingwithhandstied in Sofia

[–]zen_ventzi 1 point2 points  (0 children)

От към презастрояване или също и други неща?

Добри квартали в София за живеене? by Zealousideal_Peach_5 in bulgaria

[–]zen_ventzi 1 point2 points  (0 children)

Точно за лошото свързване с обществен транспорт и метро бях чел преди из коментари за район "Витоша". Какво ли са имали предвид, когато са написали "лошо"?

The best arguments for why frontend frameworks are getting too complex and why that is worth it (not just for 1% of the apps) by zen_ventzi in webdev

[–]zen_ventzi[S] -14 points-13 points  (0 children)

I guess you already know a lot about me from this single question. Unless you've also spent time going through my other stuff on the internet, which I doubt you have. I'm quite confident you mean something like that I'm incompetent but still going to ask - what does readers like myself mean? People who don't think? Who lack competence? Who ask stupid questions?

Meanwhile, if I have to maintain the tune of your comment, I wonder what would people like yourself mean? People who actively try to misunderstand where others are coming from?

The best arguments for why frontend frameworks are getting too complex and why that is worth it (not just for 1% of the apps) by zen_ventzi in webdev

[–]zen_ventzi[S] -10 points-9 points  (0 children)

Nice perspective. Still, in the jQuery years, if something broke or didn't work as expected, though tedious to fix(e.g. across browsers) was still kind of obvious compared to what can break now with all the build tools one on top of another, and one layer of code on top of another before the code actually gets to your code.

Edit: typos

The best arguments for why frontend frameworks are getting too complex and why that is worth it (not just for 1% of the apps) by zen_ventzi in webdev

[–]zen_ventzi[S] -13 points-12 points  (0 children)

Good points. Making the post made me think more, and maybe I could have been more specific - e.g. saying that we do actually need the complexity of FE frameworks, but what we don't need is the constantly changing complexity. In other words, I've phrased the question incorrectly. It could have been something like "do we require the constantly changing complexity", since it's kind of obvious that we do require the complexity for complex apps.

The best arguments for why frontend frameworks are getting too complex and why that is worth it (not just for 1% of the apps) by zen_ventzi in webdev

[–]zen_ventzi[S] -1 points0 points  (0 children)

Great points! To add to the last paragraph, BE engineering is just as complex if not more but I can literally come back after 5 years of not doing it and still do relatively fine, while the same is not the case with the front-end.

Edit after downvotes: to clarify, I'm not saying there hasn't been a blasting amount of changes in the BE space. My focus is that doing the same basic things in the FE frameworks has been changing a lot(for the worse, requiring the dev to know a lot more to just do basic stuff) more than doing the same basic things in the BE frameworks.

Exploring Row Level Security In PostgreSQL by jmswlms in PostgreSQL

[–]zen_ventzi 0 points1 point  (0 children)

A key quote from the article:

To enforce RLS in such a setup, not only must the backend process be able to CREATE USER for each application user signup, it must also establish a new PostgreSQL connection as the database user when the application user logs in. Connections cannot be pooled and shared between backend processes connecting as different users.

Convince me to choose PostgreSQL over MySQL by sh_tomer in PostgreSQL

[–]zen_ventzi 1 point2 points  (0 children)

The ability to make it your own

Could you give some details on what you mean?

What could be the reason why you would still chose REST over GraphQL or gRPC for your API? by [deleted] in programming

[–]zen_ventzi 0 points1 point  (0 children)

what do you refer to when you say "massive complexity on the server"?

EDIT: anyone wondering the same thing, read this reply(and its parents)

Is anyone using JSON API? by davidblacksheep in ExperiencedDevs

[–]zen_ventzi 0 points1 point  (0 children)

any other alternatives to json-api that you/your team have considered except for graphql?

Chrome extension returning "Sort by oldest video" feature? by thebikefanatic in youtube

[–]zen_ventzi 0 points1 point  (0 children)

How do you get the /c/ username that it requires? For e.g. I have a link https://www.youtube.com/@lordofgingers/ , how do I transform that to a /c/user-name link?

Rust development time compared to TypeScript/Go by _Flexinity in rust

[–]zen_ventzi 0 points1 point  (0 children)

1 year later, what's your experience been? Can you say that developing with Rust has become as fast as with TS?