jaimefjorge

I would slow cook and smoke the finest meats and allow for Europeans to taste the amazingness that is US southern comfort food.

I would make it so delicious that together with low supply of seats I would be able to charge significantly.

Our on premise product is designed for companies that require discretion and a higher security scrutiny.

We take security and data protection very seriously in our on premise product. We don't have any access to the product or machines running Codacy. We're very open to feedback and improvements and this is why we constantly are improving our policies and deployment processes. We have some of the largest and most security focused corporations using Codacy Enterprise.

Happy to answer more questions!

Codacy helps developers make great engineering decisions. We help thousands of developers ship billions of lines of code per day. We love crafting software and we're obsessed about helping developers and teams have better code.

I'm the CEO and co-founder and we're looking for someone obsessed about developer performance to lead our product team. If you're down for an adventure, move to Europe and sunny Lisbon, Portugal and help us bring the world's software quality up.

We're also looking for other positions such as Engineering lead and Software Engineer. Contact me (jaime at codacy dot com) or apply https://codacy.workable.com/jobs/500856

I've made this because all the companies that my co-founder and I met had scripts glued together in build tools to get code metrics and static analysis.

We ended up discovering a significant amount of people and companies interested in having a nice product constantly running code analysis and linked to Github.

Coming from a .NET world, you are definitely well served by great tools. Our main selling point with Codacy is that there's a higher value to static analysis tools when they are not only integrated in the collaboration workflow (i.e. Github, Bitbucket, Gitlab, etc) but also integrated with other tools. How does one discover quickly what is the code quality impact of a commit/pull request done by a team member? How about whether a pull request is ready for merge? That's what we're doing essentially.

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 how much but was the standard for the BETA category). They upgraded us to the BETA category even though we actually should have been put in the lower ALPHA one.

In any case we executed on a plan: to extract as much as we could from it and that we did:

* We abused the day with the stand to talk to Startups and give awareness of our product. We actually met a few of our best customers.

* We did a list of people we wanted to meet and took some effort to network and reach them. We got into very interesting discussions and follow on meetings after the conference. We met great engineers and people we ended up partnering with.

* We took part in the pitch competition (with some hesitation at first to be honest..), but took it seriously and we ended up winning the whole thing (techcrunch.com/2014/11/06/lisbons-codacy-wins-the-web-summit-pitch-competition/)

So while I cannot speak for these new conferences, for us the Web Summit was certainly a great investment.

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 shouldn't cover the fact that blocking the team because of camel case issues is not the best use of time. There are static analysis tools that are free and open source that can do this work.

We are spending between 1/5th to 1/10th of our time reviewing code[1]. Most of the times the disciplined have to carry the burden of being 'that guy' that always has something to say.

1: http://www.quora.com/How-much-per-day-or-week-do-engineers-s...

I had this issue and my conversion went way higher once I made my copy for my user instead of for my product.

Good luck! Your product looks amazing.

Please also take a look at a parallel discussion in proggit: http://www.reddit.com/r/programming/comments/1zqbx1/10_ways_...

From my experience in Codacy, some of our users use it to grade and quickly send out comments from the tool to the outsourced team. They like being able to review the code as it's being done (since it's per commit) with the help of our linting code patterns.

We also give out grades which is an overall vision of the project without having to go into much technical detail. "Why is this a C?" is a great question to ask :) I'd love to hear more about your experience and your pains and check if we can be of assistance. Here's my email: jaime at codacy dot com.

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 only the transaction in question.

We've also rarely touched it; it was the first time we actually messed with isolation. For the 1-5% of times, we figured it would be useful to know.

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.

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).

The article states that Akka has no true lightweight threads. The guys behind Akka have put it running with 50M messages/second[1] and perfomance vs erlang seems to be good as well [2][3].

Perhaps a benchmark would be great.

Thanks for sharing.

[1] http://letitcrash.com/post/20397701710/50-million-messages-p...

[2] http://uberblo.gs/2011/12/scala-akka-and-erlang-actor-benchm...

[3] http://musings-of-an-erlang-priest.blogspot.pt/2012/07/i-onl... (discussing millions of messages is a good signal IMHO).

So if you love your engineering, do stuff for other people!

If you love open source, join a project.

If you like the scientific side, implement a paper and open source it.

If money drives you, create an mvp for a need of a person you know has.

If you can't find that need do what I did a year ago: micro dev task delegation, i.e. rent yourself by the hour to help devs around the world (I actually published it here on HN) - it paid my vacations and I got to code for awesome people in awesome projects.

If you love good software design and awesome architecture write about your opinion with code samples demonstrating them. Hell, learn a new programming language (Haskell makes your brain tick :)).

I think a good developer that loves his craft is always a few hours away from something amazing. You probably just don't know it yet.

Disclaimer: MSc in Soft. Eng. so I know it sucks to feel the void.

However, I don't see myself copying and pasting stack traces. Would love to have something built in in my workflow. :)

1) You don't have time to refactor 2) The overhead of refactoring is too big

So for all these cases, we believe you should be able to live with the code you have and not make any inconsistencies.

Showing real life examples is definitely interesting.Will improve.

Thank you for this.

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@qamine.com)

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 introducing time whereas those tools don't have the concept of time.

If you ran those tools every single time you commit to see if you forgot to change a code region, you don't need us. If you're interested in having that ran for you, that's where we come in.

Thank you for your question. I hope to have answer it?

What we have seen is that startups don't have more than 5-10 clone detection inconsistency issues. So we want basically to provide that value for you for free. And, as soon as you outgrow that number because you have 1) a larger team 2) more code, you will be able to afford the subscription.

Aha, awesome stuff. Thank you for your love. Please let me know if you ever need anything (jaime@qamine.com/jaime.fjorge) If Qamine is essential to you, I would love to give you extra credit/bugs and a hug for that testemonial.

Thank you for sharing the love!

Thank you for your kind words!

Because it is growing, however, I can assure you that it will be our next integration :) Sign up (or ping me: jaime@qamine.com) and I'll update you.

Thanks for the interest!