Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jaimefjorge
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
15 ms
·
121.
▲
On Finding Bugs in Google's V8
(qamine.com)
19 points
by
jaimefjorge
14y ago
|
3 comments
122.
▲
by
jaimefjorge
14y ago
This makes me happy and relaxed. Personally I would really like for Typesafe to be successful with their Scala products and consulting. It would only make Scala prevail and have more support for people like me (who have Scala in their devel
123.
▲
by
jaimefjorge
14y ago
Feel free to ask questions! I would really love to hear your opinion.
124.
▲
A day in the life of Software Developers [Infographic]
(imgur.com)
3 points
by
jaimefjorge
14y ago
|
2 comments
125.
▲
by
jaimefjorge
14y ago
Just reached 3000 answers! Thank you HN for this! I am now closing this to start parsing the data. The kind people at @TrendCollective ( http://www.trendcollective.com/ ) accepted my challenge to make an infographic out of this information.
126.
▲
by
jaimefjorge
14y ago
It began as a stupid question (an error of mine).. And as expected people eat in the afternoon (82%). However, 5% eat throughout the day and 2% dont eat at all, which is interesting :)
127.
▲
by
jaimefjorge
14y ago
Here are some automated results: https://docs.google.com/spreadsheet/viewanalytics?formkey=dE...
128.
▲
by
jaimefjorge
14y ago
I now.. :( In my defense, I did not imagine so many people answering it.
129.
▲
by
jaimefjorge
14y ago
I guess gathering data. If your current task is to respond and email, then it should be considered as email time.
130.
▲
by
jaimefjorge
14y ago
To create a view like this one: http://www.inc.com/magazine/201109/inc-500-infographic-a-day... Hopefully to understand how we live daily as software developers
131.
▲
Ask HN: Software Developer Statistics (a day in your life)
(docs.google.com)
43 points
by
jaimefjorge
14y ago
|
14 comments
132.
▲
by
jaimefjorge
14y ago
Thank you! This gives us so much motivation. As a group (and previous software engineering students) we talked about this. We define that, as soon as we detect that a given task is homework or project related, we wont do it. We prefer to n
133.
▲
by
jaimefjorge
14y ago
I created a codacy github account for that purpose. Feel free to talk to us to talk about this!
134.
▲
by
jaimefjorge
14y ago
Very cool!! I will create a github codacy account right now. I'm also putting it on the site as a feature. What an awesome idea. Thanks man.
135.
▲
by
jaimefjorge
14y ago
Thank you for your encouragement! The idea of the submit > payment > success is that it should be easy for devs to get started sending problems. In the background, however, you will be able to specify a number of requirements and d
136.
▲
by
jaimefjorge
14y ago
What if you have some processing you need to make in a collection of your programming language? What if you have to make a script (in your favorite scripting language) to fetch and transform information? How about some good old SQL queries
137.
▲
by
jaimefjorge
14y ago
Those types of problems are addressed by consulting firms with thousands of employees. We are trying to be do micro consulting for that itch you have but cannot scratch it in time :) We are actually surprised by the amount of "puzzle" probl
138.
▲
by
jaimefjorge
14y ago
You're right. Trust is huge. In order to gain trust from developers we are trying to make this personal. We are responding ourselves to every email sent and talking to everybody. We dont have automated responses also because of this. We als
139.
▲
by
jaimefjorge
14y ago
I guess you have a point there. We are trying out an idea we had and the feedback is surprisingly good. Turns out there is room for type of tasks! Regarding that self contained task: well, please do!
140.
▲
by
jaimefjorge
14y ago
Thank you! Please keep it mind; we want to hear from you (even if just to talk about programming). We have experience in a number of different programming languages, different frameworks, etc.. The best approach is to send it first and we w
141.
▲
by
jaimefjorge
14y ago
Right now it isn't very scalable, you're right. However, given this positive feedback we are having, we will really consider taking people in to take care of this load.
142.
▲
by
jaimefjorge
14y ago
Cool ideas. Seriously considering them. Thank you!
143.
▲
by
jaimefjorge
14y ago
Thank you for your constructive criticism! Will work on it right now.
144.
▲
Show HN: Codacy, delegate your programming tasks.
(codacy.com)
27 points
by
jaimefjorge
14y ago
|
33 comments
145.
▲
by
jaimefjorge
15y ago
Very interesting. I guess this is always a risk when writing javascript. good mitigation though.
146.
▲
by
jaimefjorge
15y ago
Fun fact: if you're in chrome, enter ctrl+shift+j. When javascript console enters you can play with it. Try entering player.energy = 100000 :)
147.
▲
State Of Duplication: Doom 3
(blog.kamino-clone.com)
1 points
by
jaimefjorge
15y ago
|
0 comments