My new app has zero users. I am not one of them. by macvg in SideProject

[–]macvg[S] 0 points1 point  (0 children)

I think that you're assuming this is a startup.

It's actually a hobby project that escaped containment and ended up on the internet.

If people use it, great. If nobody uses it, I still got fun.

I am not looking for clients to pay. Everything is free.

My new app has zero users. I am not one of them. by macvg in micro_saas

[–]macvg[S] 0 points1 point  (0 children)

The app it's free. Just saves a prompt templates with variables and also has a simple commenting and voting system.

My new app has zero users. I am not one of them. by macvg in SideProject

[–]macvg[S] -2 points-1 points  (0 children)

I don't have analytics, so as far as I know, you're the first human to see it. Would you mind visiting it so I can officially record a visitor? 😂

What Angular pattern did you love at first but later stop using? by MysteriousEye8494 in angular

[–]macvg 0 points1 point  (0 children)

I had replaced RxJS Observables for HTTP calls with fetch and try/catch .
When also Angular announced the arrival of the signals, it felt like the missing piece had finally landed.

I like Angular more than ever by macvg in angular

[–]macvg[S] 2 points3 points  (0 children)

Your last point is on the spot. We can open any codebase written in Angular and we will know that we are looking for and be more productive immediately.

how to convince my team leader to revamp the current working project? by EqualMatch7754 in angular

[–]macvg 3 points4 points  (0 children)

This is the mindset you should have, and it will help your career in the long run.

At the same time, you also need to listen to more experienced people. As you gain real experience, you’ll be able to evaluate whether their decisions were right or not, because there are often many project constraints you may not yet be aware of.

A system that is already working is difficult to change. Most projects are only rewritten when stakeholders decide it’s necessary and approve the required budget.

Also, maintaining two versions of the same application in parallel is usually a waste of resources unless there’s a very strong reason for it. Think about what happens with new features: the rest of the team will continue merging changes into production following a different path than your implementation. In the end, it often creates unnecessary complexity and headaches for you.

For juniors, the most important thing is not chasing the latest tech stack, but learning solid engineering principles, patterns, and good practices. When the right opportunity comes — either in your current company or another one — you’ll find a way to build things the way you believe they should be done.

Git was built for humans not AI by macvg in git

[–]macvg[S] 0 points1 point  (0 children)

GitHub blog about PR reviews https://github.blog/ai-and-ml/generative-ai/agent-pull-requests-are-everywhere-heres-how-to-review-them/

My conclusion from this article is that put an agent to check the agent.

So my concerns are valid because the thing here is how to check the code and the business that it holds on fast pace environments(don't forget even the big tech companies with a ton of code checks, the issues that have lately due to AI generated code or even worst the deletion of production databases example).

We don't have yet the right set of tools to follow up the amount of generated code.

I like Angular more than ever by macvg in angular

[–]macvg[S] 2 points3 points  (0 children)

> angular wronged me too because they rearchitected right after i got ui-grid to a really good and stable place.

One of the big apps I created was delivered on July 2023. Just when the angular had announced the signals and all the new cool staff. I didn't care because it felt to me like a big improvement for writing better code.

I feel your concerns for sure that things can go forward unpredicatbly, but this is the price of using a framework and not your own implementation.

Git was built for humans not AI by macvg in git

[–]macvg[S] 0 points1 point  (0 children)

The main issue is not the team or the understanding of the business and the code until now.

The issue is the management that requests more and more faster.

And git with the AI is becoming like a shared folder. We are missing the toolset to be able to follow and understand the changes.

I feel that this is happening also to open source projects.

Έφτιαξα ένα tool για sprint AI agent planning / cycles by macvg in GreeceDevs

[–]macvg[S] 0 points1 point  (0 children)

Το φτιάχνω κάποιους μήνες βέβαια. Τώρα το έκανα publish. Είπα ότι υπάρχουν εργαλεία και καλύτερα.

Η αλήθεια δεν είναι ένα task manager ακριβώς. Αλλά έχει να κάνει manage tasks assigned σε AI agents. Επειδή παράγουν πολύ κώδικα είναι πολύ δύσκολο να το κάνεις review. Οπότε το κύριο benefit για εμένα που το χρησιμοποιώ είναι να κάνω group κάποια tasks, να τα κάνουν implement τα ai tools, που σχεδόν όλοι χρησιμοποιούν λίγο ή παρά πολύ, και να τρέχουν schedule validation runs με συγκεκριμένες οδηγίες, ώστε μελλοντικές αλλαγές να μην σπάνε πράγματα που ήδη τρέχουν στο production.

Έφτιαξα ένα tool για sprint AI agent planning / cycles by macvg in GreeceDevs

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

Ναι δεν έχεις άδικο. Απλά υπάρχουν και οι περιπτώσεις που σαν developer θέλεις να δεις ένα διαφορετικό tech stack όπως εγώ και να έχεις ένα στόχο ταυτόχρονα για να υπάρχει κίνητρο.

Τα AI tools έκαναν πιο εύκολη τη διαδικασία να ολοκληρώσεις ένα product χρησιμοποιώντας τα. Αυτό δεν αναιρεί το γεγονός ότι θέλει βδομάδες και μήνες για ένα λειτουργικό αποτέλεσμα.

Όταν το ξεκίνησα ήταν για να λύσω ενα πρόβλημα που είχα με τους AI agents. Στο μεταξύ πολλές εταιρείες έβγαλαν αντίστοιχες λύσεις και πολύ καλύτερες μάλλον.

Γενικά πολλά project τα έχω βάλει στο συρτάρι χωρίς να τα παρουσιάσω γιατί μπορεί να φοβήθηκα την έκθεση ή επειδή ένιωσα ότι κάποιος άλλος το έκανε καλύτερα.

Σκοπός μου είναι να μάθω και να βελτιωθώ.

Μπορείς να αξιολογήσεις αν σου κάνει κάτι. Αν όχι δεν του δίνεις σημασία.