Hey Nicolas,
if you have 2 frameworks, I'd not call it a single stack 😛
Simple question: why do you use angular and react for the same app? One should be enough? You can reduce the number of pinned repo to keep focus in your fav repos. The most polished ones.
Front-end developer since 2016. Focused on React with GraphQL while studying software architecture, design patterns, emotional intelligence, and leadership.
Hey Maxence! Thanks for the comments.
You have a point about the "single stack", i used that term because i was trying to simplify it, but I think I was wrong hahaha.
About your question, i am currently working in angular at work, so I can have a better version while I am building the API, but I worked with React before and I want to make a version using the same API to have both examples working. I know my react version doesn't have much work so far, but i will go for it after i get done my first 0.x version on the API.
About the empty app, it is because that version it is in a very early stage. I wanted to have a "stable" pipeline working and then mantain it in that way until I reach the first 0.x version.
At last, I understand that you can be overwhelmed with the icons, I wanted to make a more visible approach using the icons in that way. But i will keep in mind to remove the obvious ones.
I appreciate a lot your reply, any other idea you have is welcome. There is always room for improvement.
Hey Nicolas,
if you have 2 frameworks, I'd not call it a single stack 😛
Simple question: why do you use angular and react for the same app? One should be enough? You can reduce the number of pinned repo to keep focus in your fav repos. The most polished ones.
also, the link to the app seems to be empty ? mybudget-api.herokuapp.com
About the main readme, I feel overwhelmed by icons :D
I'd remove the most obvious ones. If you use React, I guess you also know/use HTML, CSS, JS...
Hey Maxence! Thanks for the comments.
You have a point about the "single stack", i used that term because i was trying to simplify it, but I think I was wrong hahaha.
About your question, i am currently working in angular at work, so I can have a better version while I am building the API, but I worked with React before and I want to make a version using the same API to have both examples working. I know my react version doesn't have much work so far, but i will go for it after i get done my first 0.x version on the API.
About the empty app, it is because that version it is in a very early stage. I wanted to have a "stable" pipeline working and then mantain it in that way until I reach the first 0.x version.
At last, I understand that you can be overwhelmed with the icons, I wanted to make a more visible approach using the icons in that way. But i will keep in mind to remove the obvious ones.
I appreciate a lot your reply, any other idea you have is welcome. There is always room for improvement.
it was just some thoughts as if I was thinking loudly.
but it's your page, your projects. So keep doing what you think it's the best ;)