Haven't posted on devrant for quite a while but I need the community's input on a decision I have to make:

I recently graduated from college and I have two job offers: one as SDE 1 from Amazon and another from a small (less than 10 people) but quickly growing start-up. I looked at all the generic pros of cons of joining an established company vs a startup but I am still torn on the decision. Both the companies are offering similar pay, so money's out of the question now.

If anyone from the community has any advice from personal experience (or specific to Amazon), that'd help me a lot.

Have a good day, everyone!

I saw this image on IBM's blog. The author was explaining how blockchain could be used to implement self sovereign identities. But, isn't the last step wrong? In order to decrypt Alice's message, Bob should use his private key instead of Alice's public key, right? Of course, while encryption Alice has to use Bob's public key.

Any ideas as to what I can do with a 24 port network switch that I salvaged out of an electronics dump?

It's only 100 Mbit though

Completing 95% of a project is infinitely more difficult than completing 70% of the project.

I am still in college studying for an electrical major and my side projects are the only dev work I do, so I don't even have any excuses to not complete them, I just jump to the newest project idea I had and forget all about the old ones until one day, several months later, I look at the code I wrote, get disgusted by how terrible it is and lose all the remaining motivation to work on it.

What do the elite 1% of the software engineers actually work on these days?

TL;DR: What do you hate about the current interview process for software dev positions?

I have been reading interview related posts on reddit and other places and I have noticed that there is a lot of hate, especially from more senior devs, towards the typical software dev interview pattern i.e. the one focused on algorithms and data structures and I don't understand why. The current methods may be far from ideal but I think they do a good job of eliminating the false-positives. Plus, I can't think of a better alternative. Sure, by using current interview methods some good devs might get rejected because they haven't used/needed/studied many algorithms and data structures after they left college, but for any big company that gets thousands of applications every year, that wouldn't be a big issue compared to the negative impact a false-positive may create. I am still in college so I maybe biased, I would like to hear your thoughts on this.

Github: Today we're excited to officially join the Microsoft family.

Me:

Need a book recommendation:

What is the best textbook on compilers for _beginners_? I am an entry level dev from a non-CS background and I have _zero_ knowledge of compilers.

Too bad #MeToo is taken, otherwise we could've used it to take twitter by storm. Thank god devrant exists.

Disclaimer: I don't intend to demean an ongoing social movement, these are just jokes.

Tabs or spaces?

A script that replaces <your project's style> with <your preference> whenever you pull and does the opposite just before committing.

Spread code not war

Github is the graveyard of my enthusiasm