If I have an existing project, sometimes I'll create a spike branch to play around with some new library in some way within that project, even if I'm not actually looking to build on it.
For example, I'm often working directly on forem so if there is some library I want to play with, I can whip up a branch and see how it could plug in quick-and-dirty to our code, as long as it is of the same ecosystem.
I always learn better when I'm building on top of something vs totally working from scratch.
Hi my name is Omar, I’m a software engineer that specializes in creating great front end experiences, primarily using react. When I’m not engineering I like to game and make music.
That makes sense. I don’t have an exciting project at the moment, so I was thinking I could maybe invent one that I could come back to when I want to learn new things.
I figure having a familiar project to re-implement might also be a good alternative to starting from scratch every time.
There might be a live open source project you could fork and keep around as your test ground. For example, you could essentially download DEV and use it as a playground for stuff you might try. Like "how would the sidebar look if I tried including tailwinds into the project and redesigned in?"...
That just came to mind, I'm not sure how well it would work if you're not invested day-to-day... but there must be similar living production codebases in a lot of domains which you could keep around as a test dummy that could help put the new thing in perspective.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If I have an existing project, sometimes I'll create a spike branch to play around with some new library in some way within that project, even if I'm not actually looking to build on it.
For example, I'm often working directly on forem so if there is some library I want to play with, I can whip up a branch and see how it could plug in quick-and-dirty to our code, as long as it is of the same ecosystem.
I always learn better when I'm building on top of something vs totally working from scratch.
That makes sense. I don’t have an exciting project at the moment, so I was thinking I could maybe invent one that I could come back to when I want to learn new things.
I figure having a familiar project to re-implement might also be a good alternative to starting from scratch every time.
There might be a live open source project you could fork and keep around as your test ground. For example, you could essentially download DEV and use it as a playground for stuff you might try. Like "how would the sidebar look if I tried including tailwinds into the project and redesigned in?"...
That just came to mind, I'm not sure how well it would work if you're not invested day-to-day... but there must be similar living production codebases in a lot of domains which you could keep around as a test dummy that could help put the new thing in perspective.