jcolella

For those of us without a subscription: https://archive.ph/4IyOF

This is possibly one of the best written articles end-to-end I have read. Excellent job telling the story

I tried asking a simple how does ActionMailer work with the rails repository link and I'm receiving an error response.

At my last company, when we were building a greenfield application, we leveraged this pattern, at a time when GraphQL was not yet available. In my new company, I look at GraphQL and realize that this solves the BFF pattern in a standardized way

Awesome work on the launch!. I was wondering what the main difference between Nimbus and something like https://devspace.sh/ is?

For those that are getting a 404 not found, here's the link from archive: https://web.archive.org/web/20220519020040/https://addyosman...

I went through the exact same thing with Google. The interview was very impersonal, never going into if I'd be a great culture fit and it was simply on the basis of if I knew how to do this algorithms problem that doesn't show if I'm a good engineer or not. Ended up in a much better company culturally, and I've never looked back

This is amazing. Great way to illustrate. What software did you use?

I used to be a big supporter and user of Sublime, using it for my day to day. Unfortunately, even though it still has faster boot time than VSC, the community around VSC is so much richer that it becomes a case of too little too late.

Just want to say this is great. Poor execution on the demo. README is incomplete. A basic getting started would have sufficed in this case.

I'm also using it as my default. I also find it great that with every release, they are pushing features that promote immutability; ReadonlyArray, and const assertions, to make developer workflow better and safer.

The addition of vulnerability scanning was the only reason our company switched back to npm from yarn. Other than that, yarn offers a great experience

I cannot agree more with this. I love being able to search and see how libraries are being used in real life projects. It definitely helps.

Interesting article. Though, the article should provide alternatives and speak to how use other types of programming paradigms might solve the issues that the person in the article is stating.

Great job. This is a great resource for a person like myself that is getting into the world of GraphQL

If you are using async/await, you also enjoy a performance boost.

https://auth0.com/blog/nodejs-10-new-changes-deprecations/

@jtokoph, maybe this can be put in the examples for the `callbaxx-promise` library that will be surely be created after.

This is great. This empowering and in general knowledge sharing on building startups is why many companies are successful here in the US. Very cool

I ended up leveraging multi-stage building with Docker and have a gradle image as my builder image, build the jar, and copy that to the image that is going to get deployed.

I know that there are many backend solutions to this such as using a headless browser to generate the page and create a PDF, and Wkhtmltopdf, but I'm looking for a way to circumvent this with a full frontend solution.

Great stuff!. Specially at the beginning, webpack is intimidating and can turn complex quickly. Wish I had this when I began. Another add-on I would recommend is the addition of the: - target: 'node'

for those developer that are using webpack on the backend.

I always say pick the best language for the type of problem that you are trying to solve. If your problem is heavy IO, than I recommend NodeJS, as that's the forte. Instead if the problem is a CPU-bound issue, then NodeJS is not appropriate. Within the NodeJS ecosystem, you can use Typescript, as well as use webpack to have an optimized build. There is always something to learn.

Totally had the same reaction. The first thing I thought of is "wait doesn't ParamStore already do this?"

Thanks @itemarhaber. That presentation was amazing and helped me understand the underlying advantages and disadvantages. I will add this to the README

Hi guys!. Wanted to share my experience with using Redis as a JSON store in NodeJS. Wrote about some potential strategies; with advantages and disadvantages, as well as some code to go along with the README.

Any feedback or experience that you want to share when working with Redis are greatly appreciated!

Very interesting project, integrating all these different libraries. One thing, I noticed that you are using a hardcoded path to the json. Created an issue for you https://github.com/minimaxir/magic-the-gifening/issues/2. Thanks for sharing your work.

"One of the areas I'm especially proud of in Sublime Text 3 is performance". I totally agree with this statement. Writing software in sublime has certainly made my life easier. Kudos to Jon and team.

Great article, specially with the sections on coverage on testing. Also, specifying the process so another can easily reproduce it. Very nice!

Location: Madrid, Spain

Remote: Yes

Willing to relocate: Yes

Technologies:

- Programming Languages: Python (Flask, Django, scrapping projects, selenium), JavaScript (Angular, jQuery), NodeJS (express)

- OS: Debian, Ubuntu, RHEL, CentOS, ArchLinux, OpenBSD

- Database: MySQL, Postgresql, Mongodb

- CI: TravisCi, Jenkins

- Docker, Vagrant

Resume/CV: https://www.dropbox.com/s/l4c1hdo7cm1e848/CV-Europass-201612...

Email: josecolella@yahoo.com

LinkedIn: https://es.linkedin.com/in/josemiguelcolella

Github: https://github.com/josecolella