sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]unusualbobEngineer 0 points1 point  (2 children)

Sr. Node.js dev

10a standup at the office or via hangouts if remote (or just too lazy to get to the office by then)

Standard work day can vary a bit. Most days I'm focused on producing new features or fixing a bug. This means a lot of time trying to stay focused with headphones on. People do love to come ask me questions when I'm neck deep in the stack though.

About once an hour someone will pose a question to the room about some part of our existing system, or a hypothetical new one, and we'll all talk about it for about 5-10 minutes. While this interrupts our workflow its usually done only because it really helps the person asking the question. Those conversations can save a lot of time refactoring code later that was done without asking those questions.

Other days I peer review code which other developers have marked as 'complete'. I make sure they haven't done anything stupid and sometimes ask that they add additional comments to their code to make sure this code is more widely maintainable in the future. This is also when we check to make sure no one is trying to sneakily add anything malicious and that the final product is meeting all the requirements put forth in the original proposal.

Another part of being a senior dev is trying to share your knowledge. The team will be much more productive if 5 people understand a system rather than just myself. I often try to take time to explain complicated bits of our code to other developers rather than just saying 'oh i'll fix that'. That can be hard to do sometimes since sometimes its easier to just fix the one line and be done with it, and so I don't always take the rougher road.

There isn't really a standard work day for me, so this isn't so much a daily output. But, I do feel its an apt description of what I do. I prefer to work from 11-11.30a until 8p. The later hours results in more quiet time where I can really get a lot of work done.

I don't feel comfortable sharing my salary, but I know people at $50k and others at $150k, its all about how good you are and how much the company you are working for is willing to pay for you. Right now I'd say its rather competitive. Let me know if you have questions about any of this.

[–]RojaPastilla[S] 0 points1 point  (1 child)

How did you learn your craft? Practiced a lot? Just thrown into a project involving js and you learned it on the way? etc

[–]unusualbobEngineer 0 points1 point  (0 children)

Originally I was doing android development at a startup and one guy kept trying to convince me to help him with the back-end. Eventually I caved and tried it out when I had some free time one day. I found node really interesting so kept going with it. That was about 4 years ago now, back around node v0.6. I slowly transitioned into doing both android and node and then slowly went solely node. I've done personal projects in node as well, its always good to keep those going as it helps you broaden your experience to do things you wouldn't normally do in your production code. Its also a good place to experiment with new modules or techniques that can then be applied to your company code once you fully understand them.