NickLarsen

8 ms·

1.
How we sped up random forest processing, lots of common performance patterns(cultureofdevelopment.com)
2 points by NickLarsen 7y ago|0 comments
2.
How we sped up random forest processing, getting the lay of the land(cultureofdevelopment.com)
1 points by NickLarsen 7y ago|0 comments
3.
Developer Happiness: The Right Tools for the Job(stackoverflow.blog)
1 points by NickLarsen 9y ago|0 comments
4.
by NickLarsen 9y ago
It's definitely hard. There was certainly no clear cut solution to any of the problems I included on the card in the picture. We evaluated 8 or 10 different solutions for out of the box stuff, found things we liked and didn't li
5.
by NickLarsen 9y ago
The localization project I use as an example here was definitely one of my top 3 hardest projects of all time (and that was years ago). It was not a particularly difficult technical challenge, it was difficult because it touched every sing
6.
by NickLarsen 9y ago
Thanks for posting this. One thing I didn't write about is the objectiveness of interviews (felt like a different topic). Just about any question can be okay as long as it follows a few simple rules. 1) if you ask a question, you sh
7.
How to talk about yourself in a developer interview(stackoverflow.blog)
441 points by NickLarsen 9y ago|191 comments
8.
by NickLarsen 10y ago
I'm familiar with the LLVM direct to wasm tool, but I was unable to get it working using the steps from the emscripten docs. The binaryen toolchain is pretty easy to digest, but I've been using the emsdk almost exclusively for th
9.
by NickLarsen 10y ago
Sounds like a processor to me, let's just call them kernels.
10.
by NickLarsen 10y ago
Initially my thought was to compare it to the first compiler, back in the days when punch cards were the interface, but I decided against any history lessons that go that far back. In that analogy, the byte code is the machine, and now we
11.
by NickLarsen 10y ago
We (at Stack Overflow) have a new documentation product coming down the pipe with an emphasis on examples and I thought it would be awesome if we could expand our stack snippets feature to languages beyond javascript. A reproducible exampl
12.
by NickLarsen 10y ago
That's fair. Originally asm.js was named capsule.js but that was taken and didn't really mean what it was. We could also call it modules but there is another very related spec out there for that as well. What would you call it
13.
by NickLarsen 10y ago
I had the exact same problem when I first started. Someone once told me "what we can throw away to solve this problem", so I kept removing parts until I got here which I think is currently the easiest way to get started.
14.
Build Your First Thing with WebAssembly(cultureofdevelopment.com)
195 points by NickLarsen 10y ago|56 comments
15.
by NickLarsen 11y ago
The last 10 minutes where you ask questions is a bad time to waste asking someone to judge your 3 year plan when they just met you. Most of these questions are better asked when you fail an interview and request feedback as to why. I speci
16.
My Andela Mentee did a great writeup after a practice interview(blog.hisabimbola.com)
1 points by NickLarsen 11y ago|0 comments
17.
Always Get/Give Interview Feedback, It Matters(cultureofdevelopment.com)
2 points by NickLarsen 12y ago|1 comments
18.
Your Developer Toolbox(cultureofdevelopment.com)
7 points by NickLarsen 13y ago|0 comments
19.
by NickLarsen 13y ago
> What are ‘presentation semantics’? I think this is a corruption of the concept of semantics. Semantics are what a thing is, or means, or does; not how it is presented Semantics just means to give something meaning. Presentation semant
20.
by NickLarsen 13y ago
Let me start by saying I am the most vocal person about semantic HTML at my company, but it really depends on your purpose, and I'm not sure you are realizing you are taking a hard line. Also, I would have preferred you used the 90% o
21.
The Correct Reponse to Shitty Technical Arguments(cultureofdevelopment.com)
1 points by NickLarsen 13y ago|0 comments
22.
Draft your code(cultureofdevelopment.com)
1 points by NickLarsen 13y ago|1 comments
23.
by NickLarsen 13y ago
I'm pretty sure the folks who have amassed "hundreds of thousands of reputation" did it merely by answering 1000's of questions. http://data.stackexchange.com/stackoverflow/query/105837/how... Sure there are a few questions with highly vo
24.
by NickLarsen 13y ago
I had honestly never heard of Joel until I did my research when applying at Stack Overflow. Didn't affect the outcome.
25.
Interviews: What I'm Thinking While I'm Interviewing You(cultureofdevelopment.com)
1 points by NickLarsen 13y ago|0 comments
26.
by NickLarsen 14y ago
Yes, with a strong bias to not forking and maintaining. Stale project, well you gotta fork and maintain. Active project, avoid forking with the intention of using a custom build in your system.
27.
by NickLarsen 14y ago
Were they actively making changes to the project and running custom builds? If not then they just had nothing to contribute to the project and there is certainly nothing to feel disgusted about.
28.
by NickLarsen 14y ago
This is exactly the pain my advice helps you avoid. The implicit cost of creating a fork is that future changes higher up the chain could either cause you to be stuck at this revision or give you an additional bulk of work in order to upda
29.
Open source and the ability to modify code(cultureofdevelopment.com)
39 points by NickLarsen 14y ago|25 comments
30.
by NickLarsen 14y ago
I have my doubts about this. Disclosure, I work for a Careers 2.0, but little of my thoughts are biased by that in this case. For starters, this doesn't even seem to fix the problem stated, "The top developers are 25 times more effective t

More ›