Me: Learn as much as you can and write as much code as you can but don’t lose yourself in programming. It’s a great career that has to be complimented with hobbies and passions. Don’t burn out 🫡
![]()
178 sats \ 1 reply \ @MarsIronPI 12 Apr
If you only know Java and C++, learn some Lisp. It’s a life-changing experience. In fact, if you come across a language that looks weird to you, learn it and absorb its ideas. They probably look weird to you because you’re looking up the power continuum. Also, learning new languages gives you the advantage of the Python paradox.
reply
120 sats \ 0 replies \ @k00b 12 Apr
Great advice. I learned a lot by hobby programming in Lisp.
reply
128 sats \ 2 replies \ @plebpoet 12 Apr
starting out, I think devs should wrestle with the ethics of turning every human function into software, (giving away ambiguity at the throne of efficiency) because there is a good and evil tension within the work that is going a little too unnoticed for my comfort
reply
0 sats \ 1 reply \ @k00b 12 Apr
I'd love to read a long form post about this. I sense there's a lot that can be said.
On the spectrum of antibiotics to gambling (or whatever might be on either end), where does software sit ethically?
reply
0 sats \ 0 replies \ @plebpoet 15 Apr
yeah I gotta define all my terms, I will write long form about what I mean. but it will be hard because I have to figure out what I mean
reply
40 sats \ 0 replies \ @ek 12 Apr
The picture would be even better when both paths merge in the distance just to fork into even more paths
reply
30 sats \ 0 replies \ @nikotsla 12 Apr
Small iterations.
reply
30 sats \ 0 replies \ @beorange 12 Apr
Like in any field and sport, you need to practice.
Java or C++? try both, then go deep on the one you feel more comfortable, keep pushing, keep building, keep learning.
reply
10 sats \ 0 replies \ @030e0dca83 12 Apr
Write tests
reply
125 sats \ 1 reply \ @SimpleStacker 12 Apr
Don't only write code for your employer. Also work on projects inspire and motivate you, even if you're not getting paid for it.
reply
0 sats \ 0 replies \ @alt 13 Apr
While this can be good advice it also puts you at risk of becoming burnt out. I do software engineering as part of my job (not even all of my job, maybe 50%) and the last thing I want to do when I have time off is write even more code!
reply
100 sats \ 0 replies \ @k00b 12 Apr
Write lots of code attempting to do things slightly beyond your current skill level.
reply
40 sats \ 0 replies \ @gd 13 Apr
If you want to become a professional software engineer, you need to understand what your role is in a business.
Software engineers are there to solve business problems with code as their tool. Focus on the business problem and the value it would bring when solved.
In terms of code writing- fix technical debt as soon as possible, don’t build new features until your debt is paid.
reply
30 sats \ 0 replies \ @Silent_Hodler 13 Apr
Learn as you go. Pick a project and learn how to get it done doing it. Remember about the simple rule: first make it work, then make it good and at last make it fast. Also remember Java Script runs on virtually everything.
reply
30 sats \ 0 replies \ @kepford 12 Apr
Others have given great advice I would also co-sign. One thing I would add is prioritize positions/jobs at companies where you can learn from others vs. simply which job pays the most sats. Prioritize learning over earning in the beginning. It will pay off later. If I could go back I would have moved to an agency job much sooner. It ramped up my knowledge and confidence so much faster.
reply
0 sats \ 0 replies \ @bitcoinplebdev 15 Apr
Learn: Learn 2-3 concepts
Build: Build something using those concepts
Push: Push it to github and back it up
Reference: reference for later when you need to reuse those concepts or code
Repeat
reply