Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jcolella
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
1.
▲
Ask HN: Documentation or getting starting with building a rules engine
1 points
by
jcolella
2y ago
|
0 comments
2.
▲
by
jcolella
3y ago
For those of us without a subscription: https://archive.ph/4IyOF
3.
▲
by
jcolella
3y ago
This is possibly one of the best written articles end-to-end I have read. Excellent job telling the story
4.
▲
by
jcolella
4y ago
I tried asking a simple how does ActionMailer work with the rails repository link and I'm receiving an error response.
5.
▲
Ask HN: Suggestions on storing entity-attribute-value model
1 points
by
jcolella
4y ago
|
0 comments
6.
▲
by
jcolella
4y ago
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
7.
▲
by
jcolella
4y ago
Awesome work on the launch!. I was wondering what the main difference between Nimbus and something like https://devspace.sh/ is?
8.
▲
by
jcolella
4y ago
For those that are getting a 404 not found, here's the link from archive: https://web.archive.org/web/20220519020040/https://addyosman...
9.
▲
by
jcolella
5y ago
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
10.
▲
by
jcolella
5y ago
This is amazing. Great way to illustrate. What software did you use?
11.
▲
by
jcolella
5y ago
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.
12.
▲
by
jcolella
7y ago
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.
13.
▲
by
jcolella
7y ago
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.
14.
▲
by
jcolella
8y ago
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
15.
▲
by
jcolella
8y ago
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.
16.
▲
by
jcolella
8y ago
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.
17.
▲
by
jcolella
8y ago
Great job. This is a great resource for a person like myself that is getting into the world of GraphQL
18.
▲
by
jcolella
8y ago
If you are using async/await, you also enjoy a performance boost. https://auth0.com/blog/nodejs-10-new-changes-deprecations/
19.
▲
by
jcolella
8y ago
@jtokoph, maybe this can be put in the examples for the `callbaxx-promise` library that will be surely be created after.
20.
▲
by
jcolella
8y ago
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
21.
▲
by
jcolella
8y ago
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.
22.
▲
by
jcolella
8y ago
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.
23.
▲
Ask HN: What HTML to PDF Angular (typescript) solution are available?
1 points
by
jcolella
8y ago
|
2 comments
24.
▲
by
jcolella
8y ago
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 u
25.
▲
by
jcolella
8y ago
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 appro
26.
▲
by
jcolella
8y ago
Totally had the same reaction. The first thing I thought of is "wait doesn't ParamStore already do this?"
27.
▲
by
jcolella
9y ago
Thanks @itemarhaber. That presentation was amazing and helped me understand the underlying advantages and disadvantages. I will add this to the README
28.
▲
by
jcolella
9y ago
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
29.
▲
Introduction to Redis as a JSON Store in Node.js
(github.com)
3 points
by
jcolella
9y ago
|
3 comments
30.
▲
by
jcolella
9y ago
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/is
More ›