There are more choices of highly hopped beers than ever.
Typically half the selection on the shelf is some kind of IPA.
127 karma · joined November 19, 2014
There are more choices of highly hopped beers than ever.
Typically half the selection on the shelf is some kind of IPA.
IPAs have routinely been the most featured variety at all the pubs I've frequented over the last 15+ years.
Breweries make them because people want them.
People want them because they are delicious.
Finding good developers is hard, and companies love referrals. Those 3 senior devs that have quit likely found a job somewhere else, and that somewhere else will be hiring.
If they remember you as the passionate helpful developer who was putting in a good effort at a terrible company, they'll probably want to throw potential job opportunities your way.
And make sure they have a way to contact you, even if you are just making a connection on LinkedIn or something.
It will save you if you use JSLint/JSHint/ESLint/etc.
In your example you will get an error about a semicolon missing after the return statement.
If your convention is to always use semicolons your editor can let you know you have made a mistake. If you don't use semicolons then you have to turn off these warnings from your Linter and you won't catch the error until you see weird results at runtime.
And that's the purposing of always using semicolons, so you can have automated tools help you.
I love perl, it is far and away my favorite language to hack stuff out in. Which is really where this language shines; quick prototypes or duct tape type hacks for pulling data from somewhere, transforming it, and sticking it somewhere else.
While there aren't as many perl centric jobs as there once was for building an entire application with Perl on a large team. That was never really Perls strength. Perl can still play a central role in your toolbox.
Much like Bash, sed, awk, grep, and the litany of other Linux tools, knowing Perl is going to enable you to do things that appear to be magic to those who don't.
We use JavaScript/Node.js, C# and SQL to develop the application my company is building, but I still reach for perl almost every day. Because it makes things easy.
I've used it to generate JavaScript and SQL code from data specification given in Excel or PDF format.
Python comes close to enabling developers to have this kind of magic up their sleeve, but I think Perl's built in CLI flags for implicit loops, helper operators for reading files, first class regex support, and such make whipping up a couple line script to solve some problem much quicker.
Texas symbols are two or more ascii characters that replace a single Unicode symbol.
Swiping left is not my default when visiting a website.
Patently false. * from Wikipedia
Python: Guido van Rossum * Master's degree in mathematics and computer science from the University of Amsterdam * Recognized as a Distinguished Engineer by the Association for Computing Machinery
Ruby: Yukihiro Matsumoto * Graduated with an information science degree from University of Tsukuba, where he was a member of Ikuo Nakata's research lab on programming languages and compilers
JavaScript: Brendan Eich * Brendan Eich received his bachelor's degree in mathematics and computer science at Santa Clara University. He received his master's degree in 1985 from the University of Illinois at Urbana-Champaign.
Perl: Larry Wall .... Well I guess he doesn't have a formal CS background. But he was literally a NASA rocket scientist. https://en.wikipedia.org/wiki/Larry_Wall#cite_ref-3
First, JavaScript is a darned good language. It has some quirks, and some down right awful parts. But they are easily avoided, and often can be automatically detected by static analysis tools like JSLint, JSHint, etc.
Lexically scoped anonymous functions, closures, first-class functions, immediately invoked function expressions, object literals, dynamic objects, are all magical once you twist your brain into really understand how to program in that paradigm.
And yes, other programming languages have combinations of these features and maybe implement them better. But if you look at the other most popular programming languages (http://www.tiobe.com/index.php/content/paperinfo/tpci/index....) JavaScript is really it for this sort of dynamic, functional-esque style programming.
And popularity matters when you are looking for support, documentation, or libraries to interact with other systems.
Secondly, asynchronous event driven programming is a truly powerful model. And while you can do event driven programming in any language. Node.js treats it as a first class citizen, with it's standard lib implemented as non-blocking with callbacks.
But what really makes Node.js so awesome is the marriage of it's dynamic nature with the event driven model. They just work so well together. Passing functions as callbacks for events just works so elegantly compared to how'd you have to do that in other languages. Building out constructs like promises or event emitters is trivial because JavaScript is so flexible.
I think Node.js gets shoehorned into doing a lot of work where maybe it doesn't make sense. I still use Perl/Python for CLI scripts. But for distributed network applications, Node.js makes solving a lot of problems way easier.