Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jaimefjorge
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
Fixing a “Too many open files” exception
(blog.codacy.com)
1 points
by
jaimefjorge
11y ago
|
0 comments
62.
▲
How to update large tables in PostgreSQL
(blog.codacy.com)
1 points
by
jaimefjorge
11y ago
|
0 comments
63.
▲
by
jaimefjorge
12y ago
Although I tend to agree with this post, we had a good experience with the only conference we decided to attend. We at Codacy decided to attend the Web Summit last year and invested the amount they asked us to put in (I can't recall ho
64.
▲
20% of pull request comments are about style and best practices
(blog.codacy.com)
2 points
by
jaimefjorge
12y ago
|
0 comments
65.
▲
Service discovery with Consul while moving to micro-services
(blog.codacy.com)
3 points
by
jaimefjorge
12y ago
|
0 comments
66.
▲
by
jaimefjorge
12y ago
"And that adds up like compound interest into making the code a lot better." Like inverse (or reverse) technical debt. Excellent way of putting why code reviews are important. I would just add that while improving adds up, it sh
67.
▲
by
jaimefjorge
12y ago
Also: https://www.codacy.com :)
68.
▲
Visualizing Scala code style – studying Twitter and Spark
(blog.codacy.com)
23 points
by
jaimefjorge
12y ago
|
0 comments
69.
▲
Review of PHP Static Analysis Tools
(blog.codacy.com)
3 points
by
jaimefjorge
12y ago
|
0 comments
70.
▲
7 Best Practices to Work with Freelancers and Outsourced Developers
(blog.codacy.com)
2 points
by
jaimefjorge
12y ago
|
0 comments
71.
▲
Grading European Banking SSL Security
(blog.codacy.com)
7 points
by
jaimefjorge
12y ago
|
0 comments
72.
▲
by
jaimefjorge
13y ago
Tip: this tweet is so much more important that saying what the tool is. It positions yourself with a problem the user has instead of just saying what the product does technically. I had this issue and my conversion went way higher once I ma
73.
▲
by
jaimefjorge
13y ago
Hi Sunir. Great questions. Hope to get more people answering this. Please also take a look at a parallel discussion in proggit: http://www.reddit.com/r/programming/comments/1zqbx1/10_ways_... From my exp
74.
▲
by
jaimefjorge
13y ago
Thanks for heads up. Updated!
75.
▲
How to be a faster code reviewer
(blog.codacy.com)
62 points
by
jaimefjorge
13y ago
|
43 comments
76.
▲
by
jaimefjorge
13y ago
Great question. So the issue that triggered this was a bug caused by an unrepeatable read. We changed the global level and it solved the problem. However, to stop this from affecting performance too much we targeted this isolation change to
77.
▲
Understanding Database Isolation levels in JDBC and Play
(blog.codacy.com)
17 points
by
jaimefjorge
13y ago
|
3 comments
78.
▲
by
jaimefjorge
13y ago
This is definitely useful. Export/import to/from excel could be a great feature.
79.
▲
Optimizing code in Scala
(blog.codacy.com)
15 points
by
jaimefjorge
13y ago
|
0 comments
80.
▲
Strongly typed actors in a loosely coupled architecture
(blog.codacy.com)
4 points
by
jaimefjorge
13y ago
|
0 comments
81.
▲
by
jaimefjorge
13y ago
This could simplify a lot. Love it. I wanted to get into trying both things so coupling it makes me happy and more incline to get into both. Thank you for sharing and congrats on making it into the Parse blog! Amazing stuff.
82.
▲
by
jaimefjorge
13y ago
Well written, good description and nice demo. Would love to see more on how this is different to (or better than) Akka. The programming model is actually close to Akka (with actor systems, supervision, receive method, message passing, etc)
83.
▲
by
jaimefjorge
13y ago
I'm with Guy Steele on this one: I like all languages ( http://www.infoq.com/presentations/Future-of-Programming-Lan... 01:45).
84.
▲
by
jaimefjorge
13y ago
Love this. Would want to use it right away. Signed up. Congrats!
85.
▲
by
jaimefjorge
13y ago
One of the most exhilarating things I have ever experienced was applying my coding skills to making stuff people can use and then (the important part) have people use it. I can't perfectly describe how awesome it feels but this is a go
86.
▲
by
jaimefjorge
13y ago
This is great. I find it's sometimes difficult to navigate through some stack traces. so good idea. However, I don't see myself copying and pasting stack traces. Would love to have something built in in my workflow. :)
87.
▲
by
jaimefjorge
14y ago
I've been finding that the messaging part is tricky. But you're right; we are still finding the perfect way for us to message what we do. The thing is that, we've been finding that the average project on github (specially those using ruby a
88.
▲
by
jaimefjorge
14y ago
Excellent point. SVN is definitely also on our roadmap. A couple of companies already asked for it. We already have a prototype version of SVN integration running.. Would love to have it running on your clients. Let's talk about it (jaime@q
89.
▲
by
jaimefjorge
14y ago
Great question. Those tools evidence your code duplication (saying the lines and code regions). We, however, show you when those code regions were changed inconsistently. We basically want to show you the effects of code duplication by intr
90.
▲
by
jaimefjorge
14y ago
Quick Update: My mongo instance on the code analysis server failed. Need to restart it. Sorry for the lack of results. Working on it.
More ›