2,017 karma · joined April 20, 2014
Parent, engineer
Current thing: Bioinformatics
I enrolled in the engineering program second, after I was sick of the poor employment opportunities associated with the first degree. During my engineering studies, it sometimes felt like my brain was being rewired, making it more suited to meet the rigors of the coursework.
I don't know if this was "in my head" or if something was actually happening on a neurological level. But, I know that the course work went from being ridiculously challenging in my first semester (pulled teeth to get B's and C's in the early days) to manageable and often fun in the last (mostly A's).
I am eternally grateful to the research and writing skills that I honed during my first degree. However, it was definitely the engineering courses that made me into the "analytical thinker" I am today. So, I think there is something to be said about what a STEM degree signals.
That quote just really drove it home for me.
I was a bad programmer for a long time. For a few years, I was an engineer and basically wrote quick and dirty matlab or python scripts to do physics based modeling and simulations. But, it was never elegant or efficient or anything that I guess you learn about in upper level CS courses.
It didn't have to be. A customer would never see the code, it would never have to perform under critical conditions, it could almost never be reused because each project data set was completely different. The code was just supposed to crunch input and produce meaningful output that could be analyzed.
I got to thinking that I was a pretty good programmer because I could write those scripts.
Then I quit that job and moved to a different country. The only job here that I managed to get was as a software engineer. Here, I learned how very wrong I was. Writing quick and dirty scripts that crunch data is easy. Programming is hard. Really really hard.
1. Patents are very VERY specific. Someone can have a patent for Thing A and you can make Thing B that is quite similar to Thing A, with just a few minor adjustments, and it is not an infringement. This is why there are tons of patents out there that describe pretty much the same thing, with very minute differences.
The takeaway is: just because Makerbot / Stratasys is getting a patent on autoleveling does not mean no one else can do autoleveling. It just means they cannot do it the exact same way.
2. A patent troll is an entity that has a patent portfolio, but has no actual products related to anything in that portfolio. They make their money by suing people (or bullying little guys into settling out of court).
Makerbot / Stratasys makes 3D printers. It is not trolling for them to file patents related to 3D printing technology. You might think the patent system is broken or feel that patent filing is not in the spirit of open source hardware (valid points which I personally share), but it is not trolling.
So, let's not undermine the legitimacy of those criticisms by conflating one particular (arguably douchey) business strategy with patent trolling (another, unarguably douchey strategy).
Despite the higher tax burden, I ultimately decided to incorporate here. Why? There were a lot of reasons, but the two biggest ones were: 1) I didn't want to worry about patent trolls 2) I didn't want to worry about net neutrality effecting my first users (we are starting local)
- Their core team does not have anyone with space experience. Success and knowledge from other sectors (looks like they all come from the security sector) does not translate. Space is a whole different can of worms. There are totally different and more constraining hardware requirements, regulations, cost levels to name a few.
They have some advisory board guys with the right experience, but they will need to be heavily involved to be useful to a team of guys coming from a security background (probably more than just as advisers).
- The costs associated with operating a satellite network are so stratospheric (badum-bum ding) that their claim about "democratizing access to data" is dubious. There is a very good reason satellite data is so damn expensive right now: it is so damn expensive to get in the first place.
They could lower some costs here and there maybe, but it would still be in the wrong order of magnitude. They would need to sell the data to a LOT of customers to be a profitable business, if they want to keep the cost of data low (this is what I assume they mean by "democratizing access). They have provided hints of some potential applications, but have they demonstrated there is sufficient existing demand for this?
Probably not. So they are essentially trying to create a new market while footing astronomical up front costs themselves. That is not an attractive risk proposition.
I hope it works because it could be very cool (space! data!). But, I remain very skeptical.
But, I clicked all the way through before reading the comments here because I found it a compelling way to tell their story.
edit: actually, I happily clicked through this: https://duckduckgo.com/about The "what's new" carousel did feel a little tedious.
That kind of situation happens all the time. Sure you could give order numbers, but names are a bit nicer.
Also, if you go in the same time everyday, you will probably see the same baristas. Then, they can write your name without even asking and it is cozy.
His response was basically that they are "trusted partner" (quotes because I can't remember the exact term, but that sounds right) of Facebook and so they get all the data somehow. Maybe they pay for it? I am not sure how it would work because it couldn't be anonymized for their service.
Anyway, he basically said that, when you combine the Facebook location based posts and FourSquare checkins (and probably location anchored Tweets too as well as others I am missing), there are so many millions of these happening everyday that some of those people are bound to be qualified for the position a company is hiring for.
...Which brings us back to problematic assumptions. Garbage in, garbage out.
It sounds interesting in theory. That is, until I got to asking about how they quantified softer qualities that employers look for, like an applicant's social skills or potential for a client facing role. Apparently, to determine this, they look at the number of "check ins" people do at locations that are not their home city while employed. Their algorithm assumes that the person is traveling for business and is therefore trusted to meet customers.
There are so many assumptions in this one example that it makes me question the integrity of the whole system. An algorithm is only as good as the person designing it. Maybe Evolv really is better than these guys at finding quantitative markers for softer skills, but I remain skeptical.
> Why? If we can reduce or remove the need for people to work, why should we not?
Well, it is because I figured people would want to feel valued and like they have a meaningful place in society. But, if people don't want to work and there is no need for it (assuming a low-scarcity future, as the author described), then sure. That should be an option too.
Instead of trying to lower costs for big companies by creating software that replaces people, we should strive to create something of value that can also employ people in meaningful numbers. Don't know what exactly, but that is the shape of it.
I would like to know how they drove the computer "crazy" (and how this maps to human neurology, if at all).