Joined devRant on 11/14/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
@root: happy hunting and good luck!!
Somewhat similar situation here. But my life cycle become one day cannot sleep, the next day I can sleep early and sleep like a log.
When this cycle is out-of-sync, I do exercise/long nap to "correct" it.
@p100sch The very same bullet that bit me, although I'm in Java. Keeping one tiny reference ends up keeping the entire chain of objects.
good hypothesis. Now, let's try to find out how to test it out.
Merging branches that started few years back and never merged. Happened to me twice during my eight years tenure, thanks to re-orgs.
* 2 Beyond Compare instances
* 4 Eclipse instances
* 2 VSCode instances
* 10+ repositories
You should start with assembly language. One does not start learning high level language without knowing what's happening on the silicon.
You do already know how semiconductor, bandgap and digital logic works right? Otherwise, start with your physics first before learning programming. Otherwise you will get lost on what's happening.
On serious note, what language you should start depends on what made you interested in programming in the first place. I happened to start with assembly language as I was interested in using ICE on Windows 95. But today, typical languages are Python, Java, C or C++.
And in my opinion, using modern IDE has its pro and cons. But for sure, IDE/Dev env will be another topics that you want to explore later on.
sicp: Structure and Interpretation of Computer Programs.
Computer science book that borders on philosophy.
Yep, lesson learned.
need the currency unit here. Ranting about USD 10k a month is quite something.
I wish this workflow has more support :(
I'm on Win10 and some of my gripes: I need some apps to be on all desktop (e.g. slack). Some apps are single instance, so opening it jumps to other desktop.
Other than tech stack, you should also consider the domain. It is more comparable or even more difficult to pick up than raw tech stack. Examples: how payment industry do things, how HR benefits usually structured, etc. This will assist you when moving in the same industry with shinier stack.
One main project and about 3 to 5 sides. But I make sure my manager become my gatekeeper so I can focus on the technical side of things.
Diving directly to code is a big no for me before knowing the greater contexts. If I onboard other senior devs, I will introduce the general concepts/model and expect them to pick up the details, and assist when they have clarification.
nested for loop sometimes unavoidable, but nested if is too prone for bugs, especially combined with conditions which needs to be bracketed correctly.
it helps to explain protocol flows. e.g. OAuth 2.0 RFC uses a simplified ASCII collab diagram.
It may be blasphemy but for me, vim is the key binding, not the editor. I put it in all sort of apps. My go to quick editor is also VSCode with vim keybinding.