Farhan Alam fa-901

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

Credit to MadHatter

WINDOWS

Use your text editor of choice or if you don't have one use Windows Notepad
Opening with Notepad may or may not result in a fancy mess

Close Spotify
Open File Explorer and paste the following into the address bar %appdata%/Spotify¤
Open the file named prefs with your text editor
Change the numeric value following storage.size= . If storage.size= doesn't exist add it manually to the end of the file and assign numeric value. This value represents megabytes. One gigabyte equals 1024 megabytes. In the end, it should look something like this storage.size=1024
Save the file

Service	Type	RAM	Storage	Limitations
👉 Adaptable	PaaS	256 MB	Non-persistent? (1 GB database storage available)
AWS EC2	IaaS	1 GB		⚠️ Only free for 1 year


	/**
	* Sort array of objects based on another array
	*/

	function mapOrder (array, order, key) {

	array.sort( function (a, b) {
	var A = a[key], B = b[key];