ben336

Kustomer | Senior Software Engineer Roles [NYC|Durham|Remote (USA)] |https://boards.greenhouse.io/kustomer

Kustomer is a great opportunity for an experienced Node.js dev: we've got a big product challenge (building the future of Customer Support software), a fun tech stack (Node.js microservices, heavy use of MongoDB/ElasticSearch/AWS, a CI/CD philosophy), and tough tech challenges (we deal with a lot of messaging and event data and the scale is growing all the time).

We're currently hiring for Senior Software Engineers on multiple teams, and are in the middle of a move to a remote-friendly structure so feel free to apply to any opening if you're in the US.

https://boards.greenhouse.io/kustomer

Kustomer | Sr BE Engineers | NYC & Durham NC | https://boards.greenhouse.io/kustomer

- Well funded ($173M) growing startup, still small enough to make an impact (<200 employees) - Modern tech stack: Node / Express / MongoDB / AWS / ElasticSearch

I'm one of the hiring managers currently looking for engineers, so feel free to reach out to me directly: ben@kustomer.com

Philosophy Of Software Design is a recent work on the subject

Amazon: https://amzn.to/2Rpu6zX

Book review I wrote a while back: https://benmccormick.org/2018/12/31/book-review-philosophy-o...

Whatcounts| Full Time | Front End Developer | Atlanta GA or Durham NC | https://www.linkedin.com/jobs/view/942692404/

Whatcounts is an email marketing company building out some exciting new technical projects. This role will be working on our new React-based UI and will have the opportunity to take responsibility for major parts of it as things grow out.

Tech stack is still being determined, but at minimum you'll get to work with React, Jest, Babel and modern JavaScript

Turning off all the light switches that have been left on in a big house though is a meaningful convenience. I think the privacy point is strong enough without having to trash people's use cases.

If by diagrams you mean charts, possibly https://jakevdp.github.io/blog/2012/10/07/xkcd-style-plots-i...

If you read the post, that is mostly the work that they're describing.

The value of PWAs with service worker support is that redownloads don't happen. That's also how they can have offline support (on Android at least, safari currently has a lest robust caching story)

Java and JavaScript are not directly related. JavaScript added Java to the name for marketing purposes. JavaScript doesn't run on the JVM like the rest of these languages

Mostly pre-es6, but this is my favorite "intermediate -> advanced" JavaScript book: https://www.amazon.com/Effective-JavaScript-Specific-Softwar...

There are gaps/things that have changed since the book came out, but this is a really great resource for understanding the core JS language.

Parent probably meant Service Workers http://caniuse.com/

Atom's 3rd party linter package is nicer than SublimeLinter (allows auto fixing, persistently showing errors throughout file, a few other niceties). Atom exposes nicer UIs for configuring things. There's more quality depth to Atom's 3rd party libs in my experience. I wrote this a while ago, it gives some idea what is possible with Atom: https://benmccormick.org/2016/01/11/the-most-interesting-ato...

Ha, yes I knew it was satire. That is always hard on the internet though :)

pretty useful skill

Why is it a pretty useful skill?

if your project was capable of running as just a series of backend driven pages, Ember probably wasn't the right choice to start with. That isn't really what it is for.

Slack is generally very reliable. I wouldn't be surprised if this is the first "real world" load test its status page has ever had.

A bunch of screencasts here: http://vimcasts.org/

And here's a post I wrote a while ago about why Vim can be so efficient: http://benmccormick.org/2014/07/16/learning-vim-in-2014-vim-...

This is about the trending news section (top right of the screen on desktop), not the newsfeed.

I think Path was the first to do this: https://path.com/

Several made this point, that Backbone is stable, not abandoned. I agree! I said so in the post. My concern is with the libraries around it. I've elaborated in this followup post: http://benmccormick.org/2016/03/09/stability-vs-decline/

FWIW, I definitely agree that this is mostly a non-event for small apps. I work on a large, actively developed web application, where the lack of strong actively maintained supporting libraries for things like form validation, rich tables, and other use cases is painful, especially since there were great projects for those use cases that are no longer actively maintained.

Instead of using Backgrid and backbone-validation or alternatives, we've been left creating an in house "tables" approach, and maintaining our own fork of backbone-validation. Neither of those things scale well.

The approach of a small core library with other libraries filling gaps as needed only works when there are good libraries that work well with the small core library :/ For some things its easy to take a "VanillaJS" library and make it work, but for others it really helps to have tight library integration.

to be clear, I don't think anyone is using all of these libraries in a single project. Most Backbone web apps probably use 2-6 of these repos. So the fact that some of them have gone stale is not in itself a problem, and is normal. The fact that nearly all of them have makes it much more difficult to build sophisticated web apps with Backbone. Everything non-trivial has to be done in an in-house ad-hoc basis, or using lightly maintained 3rd party code.

Thats equivalent to saying "if enough people have strong feelings about how you should spend your free time, you should listen to them". Would you really support that in any context that didn't involve "open source"?

Atom has a very good vim-mode that implements vim key bindings. You can do similar things to get emacs or custom key-bindings

You're changing the behavior of import. So if somebody else were to remove the seemingly unused `from jsonsempai import magic` the file would stop working as expected.

Non obvious "magic" code like that tends to be frowned on in general, and especially in the python community

Ember would be the Rails equivalent in JS-land

There are some small incompatibilities: https://github.com/lodash/lodash/wiki/Migrating

They're still mostly drop in though, most lodash differences are extras rather than modifications.

Yep. It's still young and I've seen some (quickly fixed) bugs, but it's one of the coolest editor extensions I've ever seen.

Thats a bit exaggerated unless he's working with really bad hardware/network connection. I generally see ~10 seconds. Which is still painfully slow.

Python 2 & 3 have destructuring. This is talking about having

def fxn(a, (b, c), d):

    pass

Python 3 will still allow

def fxn(a, x, d):

    (b, c) = x

    pass

//javascript

let [x, y] = [1,2]

#python

[x, y] = [1,2]

(x, y) = (1,2)