bahmutov

Wow, someone has submitted Cypress.io here - probably because we just crossed 25k stars on GitHub.

We at Cypress do read these comments, and we definitely understand both the positive and negative opinions. If you have never tried Cypress yourself - take a look at the first test page https://on.cypress.io/writing-your-first-test

Try it yourself, you might like the syntax and the developer experience. And if not - no worries, there are TestCafe, Puppeteer, Playwright, Selenium, Webdriver that might work better for you.

thank you, our small team at Cypress appreciates every little bit of good publicity

- Docs: https://docs.cypress.io - GitHub: https://github.com/cypress-io/cypress - Gitter: https://gitter.im/cypress-io/cypress

Can I humbly submit my blog? https://glebbahmutov.com/blog/ - 3 years, 350 blog posts, mostly covering JavaScript / Node / code quality

warning: posting my own website https://glebbahmutov.com/

Has links to blog / slides / github and list of GitHub projects with search. Allows people and myself to quickly find something. Getting recruiters' pitches (and occasional hand crafted emails to join teams) every day.

I have been using Dokku for a year for personal side projects and it has been awesome. Each release brings good features, fixes bugs and in general improves it.

Setting up could never be easier (read https://glebbahmutov.com/blog/running-multiple-applications-...) and the large number of plugins for databases is a huge plus.

We use "bates" https://github.com/luiscarli/bates by our own engineer

I blog at https://glebbahmutov.com/blog/ as a reminder to myself how some problems are solved. Now people at work, especially new hires, comment how 50% of my communication or answering questions are just links to the blog posts.

That's why I recommend using PouchDB to work with whatever API is available. Storage limits are harder to work around, but if your HTML snapshot weights more than 50MB (or even 1MB!) that it is a problem by itself.

The app saves its state in whatever form it wants. The demo saves it in localStorage that is very limited. One really should look at something better like IndexedDB or WebSql (or something that hides the technical details, like localForage or PouchDB).

seems to flash for me, add a few todos and then hit reload

ok, server-side rendering, why don't you run the entire server inside the ServiceWorker then for speed? https://github.com/bahmutov/express-service

Exactly!

The blog post author (Gleb Bahmutov) here.

Thanks for commenting, this is a cool experiment I worked on, just trying to eliminate the bootstrapping delay. Will be happy to answer any questions here, via issues in the demo repos (https://github.com/bahmutov/instant-vdom-todo), or in the library repo https://github.com/bahmutov/bottle-service

The demo itself runs from https://instant-todo.herokuapp.com/ (please use Chrome or Opera or enable ServiceWorker in the Firefox for now)

PS: Here is a little bonus, my current exploration where ServiceWorker might be useful - run your server (like ExpressJS) inside the ServiceWorker ;) https://github.com/bahmutov/express-service

The only one anyone needs - is the list of fake todos, generated using https://github.com/bahmutov/fake-todos

See demo at http://glebbahmutov.com/fake-todos/

Take a look at https://github.com/bahmutov/PE-N-starter - PouchDB (which later can proxy to CouchDB), Express and Node. Much better DB and no locking you to any rendering framework. Comes with GitHub integration plugin. Demo at http://pe-n-starter.herokuapp.com/

Well, consider that you have not paid anything for these packages, can you complain that authors do not follow the semver?

If you want to protect yourself and upgrade reliably - there are tools, like my https://github.com/bahmutov/next-update - runs your tests and only keeps upgrades that don't break stuff.

While the author is down on automatic file name scans, I see nothing wrong in using tools to catch easy mistakes. How many people do regular code / package reviews? Did not think so. I recommend: - https://github.com/jandre/safe-commit-hook - my fork of the above for NPM js workflow https://github.com/bahmutov/ban-sensitive-files - NPM checklist that includes sensitive file reviews https://github.com/bahmutov/npm-module-checklist

Finally, if GitHub can automate some of the simple checks, so can we, for different tools and environments of course.

A way to handle sequences of events - which is really powerful abstraction. Look at this (shameless self-promotion) presentation https://slides.com/bahmutov/javascript-journey-boston-code-c... and the companion blog post http://glebbahmutov.com/blog/journey-from-procedural-to-reac... plus repo of the code that shows every style of JS, including Redux and Reactive https://github.com/bahmutov/javascript-journey

I like asking a refactoring / functional programming question in JavaScript like this one http://glebbahmutov.com/blog/functional-js-interview-questio... trying to make the candidate work through several small steps. At each step (step itself is pretty simple) I am looking for clarity and the candidate being able to explain the logic and the solution.

Use next-updater - tested dependencies update for projects in bulk. Npm publish, github tag, push, etc. Flexible ranges (major, minor, patch), etc. You control everything. https://github.com/bahmutov/next-updater built on top of next-update https://github.com/bahmutov/next-update

About prediction #1 - here is micro angularjs demo showing angularjs digest cycle running in separate worker http://glebbahmutov.com/blog/run-angular-digest-cycle-in-web...

Interesting post, not sure I agree that the points raised mean AngularJs is a bad choice. Consider first objection - two way binding. Not only there are user-space solutions (bindonce), but now there is standard one-way binding in ng v1.3.

The Angular does nice job allowing simple interactive apps to be written in 30 minutes by anyone familiar with HTML and JavaScript. At the same time, if the app performs what is needed by the client, the app can be profiles, and each bottleneck can be optimized in a couple of steps.

For example, we went through this process and described the steps we used in http://bahmutov.calepin.co/improving-angular-web-app-perform...

This point-free programming style is good thing but requires knowing the exact method signatures. Luckily there are ways to easily adapt callbacks http://bahmutov.calepin.co/point-free-programming-is-not-poi...

You want great programmers? Exceptional? Why would any exceptional programmer go to US on H1B visa? It is such a short leash - no way anyone truly great would trade Europe or Asia for a chance to be a slave in a cubicle, ready to be fired at moment's notice.

You want exceptional programmers, Paul? I will tell you a way to find the truly great ones, and promise that other developers will NOT be against it. Any developer can come here, provided that the hiring company:

1. Pays him / her $1,000,000 (1 million US dollars) per year, tied to inflation. I don't care how you search or decide, but that is the best indicator of a truly exceptional programmer - paying him / her a LOT. 2. If the contract is broken for any reason, the exceptional developer gets the severance package, for example a 6 months salary.

Hmm, I do not see you or anyone else advocating for exceptional salaries to pay for an exceptional programming talent. Case closed.

I ask a JavaScript developer to debug a small problem and then come up with functional approach to solve it. Makes for good step by step exploration. Each step can be expressed in single English sentence and then coded directly into JavaScript. Much more precise than designing OO hierarchy.

http://bahmutov.calepin.co/functional-javascript-interview-q...

same with `npm home <pkg name>`

Are we really now complaining that the fast pace of new tools is a problem? Not to put everything in black and white, but would the author prefer new releases every 5 years? Just apply same principles to picking new tools like you would when buying a car: do you really need it? Can you afford it? Does the new model have something the old one does not?

Read "Functional JavaScript" and "JavaScript Allonge" books from this list http://bahmutov.calepin.co/javascript-books.html

Also, I have been blogging a lot about functional programming in javascript with practical code examples http://bahmutov.calepin.co/tag/functional.html

In particular how to go from imperative style to functional to reactive in JavaScript http://bahmutov.calepin.co/journey-from-procedural-to-reacti...

Trying to ride the wave: I have written about functional programming in javascript, see blog posts http://bahmutov.calepin.co/tag/functional.html - Ramda is great!