I've been working as a web developer for 20 years. Have written services, low level C code, etc. I'm currently studying user research, to better understand how to build products.
I love to be helpful. DM me.
No blogs yet.
Stored procedures were very popular in the 90s and early 2000s. In my opinion, it started to die out because of a couple of trends: Companies moved away from having dedicated DBAs Software Developers took on database design and implementation Writing portable software meant using standard SQL from the application layer to avoid database vendor lock in Version control (CVS, SVN, git) was easier to do on application code and hard to do on stored procedures Software releases and rollbacks are easier in application code Databases are often the scaling bottleneck, moving more responsibilities into the application layer can scale horizontally
Be excited that you are one of the first million programmers to have ever existed. 100 years from now, there will have been a billion technologists since Ada Lovelace started the practice of programming.
Did they give you a guideline like Ramiro Berrelleza suggests to his candidates? As Bridget Sarah points out, it is really unfair to assume you have unlimited time. I would timebox it to one evening after the interview, unless I got some specific guidance. Perfect is the enemy of done :) You'll get diminishing returns if you spend too long on it. I started this process with Github a few years ago, stressed out about it and finally turned it in. They never got back to me... So ya, if I could take those hours back, I would ;)
Tried it "not interested" is a bit harsh... but I'm definitely not using it as my main browser. I think the BAT cryptocurrency built in and paying websites you visit is a cool idea. I fire it up for certain privacy use cases. I trust Firefox, Brave, and Safari more than Chrome in this regard. I feel like it's the early 2000s... some websites only work on Chrome now ;(
I agree with j 's answer, the payoff of learning Assembly probably isn't as high as other topics like, programming paradigms, distributed systems, and data storage. I think a better investment would be to learn several high level languages, over the course of several years: A compiled language A functional or "other paradigm that is new" to you language Next, learning C would be a good choice to learn low level details and how modules of code are linked together under the hood. Lastly, Assembly. Many, many years down the road. I learned Raspberry PI assembly very, very late into my career. A year or two later, I did the nand2Tetris, which was really awesome. For me, a good rough guide is to learn a new language every 18 months. Rust is my current hobby horse.
Yes. That book sounds useful! I've found the book "Cracking the Coding Interview" helpful. I've been interviewed probably 40 times... so painful. I've interviewed others 100 - 150 times. These numbers are over 20 years. I have done volunteer mock interviews to help others prepare for whiteboard interviews. I'm just curious how people think about these issues in 2019.