231–240 of 292 posts
Wouldn't it be hilarious if their secret sauce analysis turns out to be a secret backchannel to the CIA/NSA and not some fancy algorithm.
You'd hope the NYPD knows how to set up a firewall and how to detect data exfiltration at that scale.
Earlier quoted context omitted.
I interviewed there in 2012. The engineer called me, did his little talk and we jumped into the questions. His first question was the subset sum problem. The literal problem. It wasn't even couched in a practical application. So I said "this is subset sum. You can solve it with dynamic programming. I would look it up in a book." His response was "but I want you to solve it." I stopped the interview and thanked him fo…
Lol. Actually, they are the kind of questions us really sr people ask to ensure people are willing to actually do work. Anyone who brushes off a question stating that it's beneath them is going to get walked right out of the building by my team.
Earlier quoted context omitted.
Lol. Actually, they are the kind of questions us really sr people ask to ensure people are willing to actually do work. Anyone who brushes off a question stating that it's beneath them is going to get walked right out of the building by my team.
Which team is that? I'd like to know so I can avoid it.
Earlier quoted context omitted.
Just curious, do you have direct experience with big companies using R, python, etc in production? My sense from working with people from those companies (and a few internships at those companies) is that you could use something like R, matlab, or scikit-learn on your own workstation with a tiny data sample to explore the data, but then do crunching by translating that program into some Java or C++ code (sometimes us…
Having worked with several large (fortune 500) data science teams, they generally do their development in Python and then throw their models over the fence for us to productionize with Java. The major difference I've seen between most of these companies is whether they've embraced Java 8 yet.
Earlier quoted context omitted.
I think I lost some points with them a long time ago during an interview when, while trying to determine exactly what the "Forward Deployed Engineer" role that I was interviewing for actually meant, realized that it was actually just that of SWE consultant, a job which I'd previously held. So I kept referring to my extremely relevant experience from previously being a consultant, calling it as such, and that rubbed t…
Having been a "salaried contractor" for my second job, I learned to avoid those positions like the plague. When customers stop buying the company's software, guess who's the first to get the ax? Also, you get to sit by and watch project managers agree to all sorts of outlandish features that you'll be stuck implementing.
As for getting the ax, that didn't happen to me, but even if it had, I've never had problems finding a job, nor have I ever lived paycheck-to-paycheck. It'd be inconvenient but that's about it.
Earlier quoted context omitted.
Would you still use it on the client side today?
Assuming that I can't get away with a web app, and need to install something native on the client side... is cross-platform support required? If so, then your choices are: 1. Write separate native clients for Windows (in C#) and OS X (in Swift or Objective-C), and perhaps Linux (in whatever). It'll be hard to hire people who can work on all three, so you'll need more headcount and organizational/technical complexity.…
Earlier quoted context omitted.
I clearly blamed a lot of things in addition to tooling in my post. My overall point, which I don't think you quite got, was that language choice doesn't matter so much compared to all those variables, and that I'm much happier and more productive now working in a less "sexy" language because of those other differences.
I think the only comment you can make is that, ceteris paribus, newer tech stacks indicate some awareness of newer ideas (who include agile / devops tooling). Old tech might, but also might not. I'm more inclined to think that Palantir's problems are inherent to the enterprise revenue equation. "Features and code quality that aren't contractually mandated" = profit The more things you can put in that category, the mo…
Earlier quoted context omitted.
Assuming that I can't get away with a web app, and need to install something native on the client side... is cross-platform support required? If so, then your choices are: 1. Write separate native clients for Windows (in C#) and OS X (in Swift or Objective-C), and perhaps Linux (in whatever). It'll be hard to hire people who can work on all three, so you'll need more headcount and organizational/technical complexity.…
I kind of wish that Sun had never come up with applets. Java in the browser was a bad idea from so many different perspectives.
I wish that applets had never been invented, too. But only because of market confusion. So many people who don't know anything about Java mix up applets (which haven't been relevant in almost 20 years) with Swing or JavaFX desktop apps, think that security vulnerabilities found in the browser plugin mean that standalone Java apps are "insecure" in general, etc.
Earlier quoted context omitted.
I moved from a "sexy" NodeJS stack at my last job to a staid Java 7 stack at my current job (we can't move to Java 8 until App Engine supports it). The code at my current job is much better written, is more thoroughly tested, and is more pleasant to continue development on. The codebase at my previous job was a rat's nest, caused primarily by lower-skilled developers, no time allocated to technical debt or refactorin…
I recently took a job. Great team, great company, interesting problem, relevant work. Everything's nodejs, but I didn't worry. How bad could it be? While the prize for Worst Tech Used in a Professional Setting might go to InterSystems Caché ® (syntax errors will bork your entire runtime, with no undo). And it's all downhill from there. Nodejs (javascript + libuv, aka control flow obfuscation framework) is a strong co…