₦airaland Forum

In my last project , the social media app I built. I wanted to select the number of comments that a post has while getting the posts from the database at once using eager loading. I was able to implement it on my local machine using “sequelize.literal” method of the sequelize ORM , but when I deployed it , I was getting an error , “comment.postid not found”. I tried to fixed it , browsed through the whole pages on stackoverflow ( not really all the pages ) , yet no show. So I decided to leave out the feature. But I was loosing sleep over it. Think about it , while browsing through posts in a social media app, if a post has comments, users should see the number of comments, when they now click the posts, they can then see the comments.
So yesterday, I decided to give it one more shot. I found a blog post that suggested using “sequelize.fn” method. So I tried it, and the error was gone, I landed into another error, something in the line of “group by “ and “aggregate functions”. I had to go and read about aggregate functions. Long story short, I was able to get it to work, went and took a bottle of beer to congratulate myself.
So my question is, is it advisable to abandon a feature you want to implement or a whole project entirely because because something is not working ? Or do continue to search for the solution until you find it before moving to the next project?

Link to the app: https://luppi-react.herokuapp.com

Hmm.... for me I'd say don't let one feature over delay u in implementing others, just circle it and move to the next.


Naturally the solution will come to u....
Sometimes you'd just sit out somewhere drinking that beer and the solution will just come to u.... like you won't even know when it hits u.... and you'd be like... "So na this thing I the here the kill myself since"

GREATIGBOMAN:
Hmm.... for me I'd say don't let one feature over delay u in implementing others, just circle it and move to the next.


Naturally the solution will come to u....
Sometimes you'd just sit out somewhere drinking that beer and the solution will just come to u.... like you won't even know when it hits u.... and you'd be like... "So na this thing I the here the kill myself since"

Nice one, that’s what I will be doing from now on, circle it and move to the next. I waste a lot of time on projects because when I get stuck I don’t move on until find the solution. Thanks for the idea.

I have more abandoned projects than completed ones Mostly because of trying to do something unrealistic for a single individual.

To your answer sure why not? Another approach is to plan your personal projects the same way your product manager and tech lead does. This will help you research more about the implementation before you write a single line of code which thereby the problem would've been solved before you jump into your IDE.

great app btw

Seems like a question for Scrum Masters. It's actually good to see you finally found a solution to the problem tho.

Enceladus:
I have more abandoned projects than completed ones Mostly because of trying to do something unrealistic for a single individual.

To your answer sure why not? Another approach is to plan your personal projects the same way your product manager and tech lead does. This will help you research more about the implementation before you write a single line of code which thereby the problem would've been solved before you jump into your IDE.

great app btw

Thanks bro

I have found that revisiting a problem works

If it gives you too much trouble, take a chill pill that moment and revisit later. Always works for me

chukwuebuka65:
In my last project , the social media app I built. I wanted to select the number of comments that a post has while getting the posts from the database at once using eager loading. I was able to implement it on my local machine using “sequelize.literal” method of the sequelize ORM , but when I deployed it , I was getting an error , “comment.postid not found”. I tried to fixed it , browsed through the whole pages on stackoverflow ( not really all the pages ) , yet no show. So I decided to leave out the feature. But I was loosing sleep over it. Think about it , while browsing through posts in a social media app, if a post has comments, users should see the number of comments, when they now click the posts, they can then see the comments.
So yesterday, I decided to give it one more shot. I found a blog post that suggested using “sequelize.fn” method. So I tried it, and the error was gone, I landed into another error, something in the line of “group by “ and “aggregate functions”. I had to go and read about aggregate functions. Long story short, I was able to get it to work, went and took a bottle of beer to congratulate myself.
So my question is, is it advisable to abandon a feature you want to implement or a whole project entirely because because something is not working ? Or do continue to search for the solution until you find it before moving to the next project?

Link to the app: https://luppi-react.herokuapp.com

Yes, I remember one game I was working on a while back. Also my second to last react project, I didn't implement local storage functionality cos I was getting errors, though it was just supposed to be an added feature I wanted to do that's why I abandoned it

NEUDUDE:
I have found that revisiting a problem works

If it gives you too much trouble, take a chill pill that moment and revisit later. Always works for me

That's what I also do, then I'll just be eating the solution will just come to me

Fourpockets:
That's what I also do, then I'll just be eating the solution will just come to me

Exactly lol. I was forcing myself to solve a problem for 2 days haha i wish i knew better then . I just ignore the thing completely came back a day later with fresh intuition and voila. Like magic it didnt take me 15minutes to solve it lol

chukwuebuka65:
In my last project , the social media app I built. I wanted to select the number of comments that a post has while getting the posts from the database at once using eager loading. I was able to implement it on my local machine using “sequelize.literal” method of the sequelize ORM , but when I deployed it , I was getting an error , “comment.postid not found”. I tried to fixed it , browsed through the whole pages on stackoverflow ( not really all the pages ) , yet no show. So I decided to leave out the feature. But I was loosing sleep over it. Think about it , while browsing through posts in a social media app, if a post has comments, users should see the number of comments, when they now click the posts, they can then see the comments.
So yesterday, I decided to give it one more shot. I found a blog post that suggested using “sequelize.fn” method. So I tried it, and the error was gone, I landed into another error, something in the line of “group by “ and “aggregate functions”. I had to go and read about aggregate functions. Long story short, I was able to get it to work, went and took a bottle of beer to congratulate myself.
So my question is, is it advisable to abandon a feature you want to implement or a whole project entirely because because something is not working ? Or do continue to search for the solution until you find it before moving to the next project?

Link to the app: https://luppi-react.herokuapp.com

awfar the project?