You could write the logic in a more straight forward, but less composable way, so that all the logic resides in one pure function. This way you can also keep the code to only loop over the users once.
I know this article and comments here are mostly related to 1:1s with your boss. But I also use them in a not boss related situation, like scheduled 1:1s with an architect or ux designer if they are not fully assigned to a team.
As a frontend developer I also encounter I need Geometry from time to time. I used it a lot in my days as a flash developer drawing vector graphics programmatically.
I feel that its missing from this list. I rarely see geometry mentioned on these kinds of lists?
You can do a lot of geometry with linear algebra. (And that's more or less what you'll have to do on a computer anyway. Ruler and compass approaches won't cut it.)
I quite like geometry for itself, but it's probably more of a niche for most programmers?
I used to share this opinion as well, until I started working on an internal library that was created by a skilled developer. He had very good test coverage and good quality tests, which turned out invaluable, once I got on board. We tried to move to library towards being fully typed in TypeScript, just to get some experience with TypeScript. Our first thought before starting was, that it would help, but didn't expect it to have a significant impact. During the port to TypeScript (and being strict on typing everything possible), we soon found numerous unexpected behaviors in the code. Some of the issues found, could have been found by a linter, but other things like models changing over time was only found due to adding static types.
After this experience I changed my opinion towards the value of static types, from being more than a nice to have feature.
One I've never thought of using before is the:
isAwesome && alert("yay");
I have used the name || "no name" operator a lot and thought to myself that it looked cool on first impression. But having something like:
isAwesome() && alert("yay");
Already makes it harder to read I think. I'm curious to what others think of this one? Maybe its just because it is new to me..
I find constructs like isAwesome() && alert("yay"); confusing as well, but in our codebase it's pretty much standard to use a simple falsy check like 'callback && callback()' for optional callbacks, but we don't use it anywhere else.
To be honest, I like and use some of those, especially when writing experimental/disposable code, but otherwise I try to be gentle to less experienced developers and my future self.
As of #5 - I used to do and love this when writing unit tests. At the end of the work day, if I'm in the middle of implementing a feature, I'd commit and then write the next unit test (inevitably) sitting in my head and leave it failing. Really helps when it's Monday.
I don't think I've ever misread that style (usually the function being called makes it obvious), but it relies on short-circuit evaluation which doesn't carry over to a lot of languages - http://en.wikipedia.org/wiki/Short-circuit_evaluation
C is particularly dangerous because it will normally short-circuit, but the standard doesn't require it and in rare cases the compiler will optimize it out.
I agree that it's ugly, but also in some languages you can get into trouble because of operator precedence. This is why ruby and perl have the operators `or` and `and` as well as || and &&.
it is also useful for cross browser debugging. having a console.log() in your code running in IE will cause problems if the console isn't actually open. If you use window.console&&console.log() you can be sure that it wont hurt your code running in IE.
Yes the Griptape is an essential part to make high ollies consistently. However ollie's are possible to do without griptape as well. Just a lot harder because you'll have a lot less control.
The harder you slam down the tail of the board the more friction you get, the easier it is to pull the board up/forward.
Hmm.. Might just be me, but isn't that half of the job of the reviewer, to decline a PR if it isn't fixed? The one making the PR should get a notification that it is declined. Their ball.
Yes, but as noted in the post, if the pull request author misses that email notification the request goes into a purgatory. And the pull request page has not way to glance down a list and note who's on what.
This isn't an individual notification system, it's an easily-scanned list of PR states, which has quite a bit of value for many projects.
email.sendBulk(generateExpiryEmails(db.getUsers(), Date.now()));
reply