3 ms·
This sounds like good advice. Don't worry about Containers, deployment or testing "best practices" until you really need it. You'd be surprised at how many sof
by lytefm 5y ago
This sounds like good advice. Don't worry about Containers, deployment or testing "best practices" until you really need it.
You'd be surprised at how many software companies' testing is "clicking around in the app", deployment is "upload to store/ rsync to server" and containers aren't used at all.
Start learning React (you can also take a look at Vue), do some tutorials and build some CRUD app which has a database.
Stay focused on the front-end, learn "just enough" of everything else when it comes up. I'd recommend getting into Cross-Platform Web app development using something like Electron (Desktop) or React Native/ Ionic (iOS/Android).
After learning the basics, dive into some frontend-heavy open source project that uses your framework, figure out how it works and try to fix some bugs.
For example, this is a Markdown editor using Vue and Electron:
https://github.com/marktext/marktext https://github.com/marktext/marktext
- vanusa 5y agoYou'd be surprised at how many software companies' testing is "clicking around in the app", deployment is "upload to store/ rsync to server" and containers aren't used at all. Not only that - a non-dockerized, bare-metal, but otherwise cleanly coded "rsync to server" app can be -- compared to the usual non-spec'd, undocumented cluster-f hairball shoved into a container, with a shiny layer of CICD thrown on top -- can be surprisingly joyful to maintain.
- jraph 5y agoAnd it's usually not the frontend/backend developer deploying the app, but a dedicated person in charge of deploying / maintaining the infrastructure. But it helps to have an idea on how they work.