Junior/mid-level web & game developer, part-time photographer, gamer, music appreciator, bmx rider, fire performer
Nothing here yet.
No blogs yet.
In the example you gave, // Instead of using this way myAwesomeArray.some(test => { if (test === "d" ) { return test } }) // We'll use the shorter one myAwesomeArray.some(test => test === "d" ) the two functions are not equivalent. In the first case you return either an element of the array or undefined (as opposed to the real boolean returned by the second case). It will work here (as the returned value is either truthy or falsy), but might give you trouble in other cases. The long version of the second function would be the following: myAwesomeArray.some(test => { return test === "d" ); }
I don't see any discrimination in either of these, but "Early Career Dev" is definitely a new term to me and sounds a bit weird. What's bad about "Junior" to begin with? Everyone has to start somewhere. All in all, I think everything should come with some context. People learn at different rates. Times change. What could've been categorised as a "Senior" 5 years ago might be more fitting for the "Mid-level" term from today's perspective.
Tim Van Dijck It's also not legal not being paid according to a contract, but here we are. This is, as I see it, a way to subtly f**k with the client if it's a small project where you don't really care if you'd get paid and you don't want to deal with the court, lawyers and so on.
It was about time. I don't think single developers paying for private repositories was a huge part of their profit, but I believe they've lost some users to BitBucket, GitLab and other services offering that for free because of that.
Currently using two (one 27" 2560x1440 as main and the old one - 20" 1680x1050 as secondary) which makes me closer to the left one than to the right. I don't see myself using more than two, although if I had the space for a third one, it would probably just sit with the desktop visible and a Rainmeter clock on it. I think about moving to a 34" 3440x1440 and relegating the 27" as a secondary. Once you get used to that amount of pixels, 1080p starts to look small; on the other hand, I do occasionally game, so 4K would be a bit of an overkill even for the GTX 1080.
One thing I might add to #2: npm config set save -exact true This will make any invocations of npm i package --save and npm i package --save-dev nail down the latest currently available version of package without making you have to remove the caret manually. And yes, npm i is a default alias for npm install (as is npm isntall while I'm at it).