News for hackers. Stuff that matters.

tinyrama

Re:nvm on Monday October 21, 2019 @05:03AM (#21310403)
Can you expand on this a little?
Re:nvm on Monday October 21, 2019 @05:00AM (#21310391)
What’s broken and how?
A developer should think of the value of their labour and how much surplus labour is being extracted. You can determine whether you’re better off working on your own project and receiving 100% of your works value or working on an established project that will pay more than your work could amass on it’s own. Furthermore, evaluating new job offers based on their level of security, growth potential, etc—based on your economic knowledge—is a good idea.

Last but not least, your economic ideals and positions will play a part in matters like licensing; e.g. you may want to be part of something that has a strong open source component/contribution level.

Re:IMHO: The Mythical Fullstack Engineer on Saturday October 19, 2019 @07:59AM (#21298021)
It seems the latest term is "full-cycle" developer. You must know FE and/or BE, plus how to test, release, etc.
Re:IMHO: The Mythical Fullstack Engineer on Saturday October 19, 2019 @07:56AM (#21298016)
What drew me to software development was the desire to make things. It's not possible to make software worthy of today's audience without front-end, back-end and release engineering.

So if this person is saying "you can't make anything yourself[1]", that would be a sad situation.

For me, and I know this is common, my backstory goes like this: HTML -> PC building -> Photoshop -> graphic design -> web design -> CSS -> PHP -> JS & jQuery -> Node.js -> Mongo/Postgres -> Angular -> React -> React Native -> Heroku -> Docker -> Gitlab/CI/tests -> ArangoDB -> Kubernetes -> CDNs and lots more

I simply do what I need to do to make stuff. I've made back-end REST+WebSocket frameworks, cross-platform front-end component libraries, database ORMs and query builders, mobile apps published on the App Store, built CI pipelines for test and release, and configured containers, orchestrators and CDNs (which I programmed) for max availability. And I've lead teams in doing all these things.

Are my experiences "mythical"? No--but if you set your own standards or definitions when defining something you oppose, you'll often prove yourself right. While I've made route-finding systems and address search services, I honestly don't know some of the algebra about sorting algorithms. I learned as I went; and while I probably need more study and a little more time on new tasks than those who focus on a narrow aspect, I'm eager to do it.

In my pursuit of making stuff, what's expressed in this article won't stop me.

[1] Of course, nothing is made ourselves, we all rely on open source code, computers and servers.