maurusrv

Thanks for the warm welcome Peter!

Some offhand observations:

1. One technical specific comment is comments behave like inputs. Maybe it's my fault but, I can't seem to use Shift or Alt Enter when writing a reply comment, i mean like a textarea. Actually, I am writing this on my editor so I get to write my reply easier before copy pasting it. 😅

2. On app uniqueness - A bit of my background is i do dev work fulltime and teach web dev on the side, so I think I can really use this to track my progress in my tech career. Comparing to others my current thoughts are: Linkedin surely is for networking especially when applying jobs so thats that, github profile can serve as an online resume too that's closer to code contributions, but polywork seems to focus more on documenting success (I found polywork from this link: https://github.com/readme/guides/document-success, shared by our CTO in our slack.). Closer to a personal blog, but more of a timeline i guess, like a social network maybe, but for doing career wor

maurusrv

Folder Structure

Please note

While this gist has been shared and followed for years, I regret not giving more background. It was originally a gist for the engineering org I was in, not a "general suggestion" for any React app.

Typically I avoid folders altogether. Heck, I even avoid new files. If I can build an app with one 2000 line file I will. New files and folders are a pain.

maurusrv

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5

Heading 6

---

Paragraph