Yep, that was it. Man, I really misremembered that. It's an Objective-C thing, which makes sense, because it was for an iOS position. I knew the idea behind it, but I had never encountered the term. I do remember I ran into it again while preparing for interviews again a year ago. I'm deep in .NET territory for work and Python for fun right now, so my iOS knowledge has atrophied a bit.
Yep, I lost an interview about ten years ago in part because I had not encountered the magic term "duck typing" yet. Never mind that I had be making file-like and string-io objects in Python for years by that time.
Don't get me started, tech interviewers are so bad...
I'm a young dev (26) that works with a lot of older developers (40-50) rather new to the field. My biggest annoyance with the older inexperienced devs is that they DON'T ask questions resulting in very bad design decisions. Keep asking questions but maybe frame them differently. i.e. instead of "How do I do this?" say "I'm planning on implementing it this way, do you think this will work or is there a better way?" This shows that you did some research and value their opinion.
Yes these were my biggest problem with this post; they don't spend the time to try and find out bottlenecks and when they finally do instead of investigating the WHY they're thinking about simply switching to yet another which is going to have the same issues if they're not using an optimal data model, etc.
This is unfortunately a very common problem-solving approach. I've seen devs upgrade jQuery because they're getting a 500 error from a PHP app. No relation to the problem - it's just flailing around in hopes something random works.
> NoSQL is a database choice now, a worse choice in my opinion.
If that's legitimately your opinion on that topic then I suggest you expand your knowledge.
NoSQL databases aren't slot in replacement for SQL databases. However, for what they're good at they're REALLY good at it. Namely highly scalable, Document Storage (or "blobs"), and incredibly low latency reads.
Keep in mind that NoSQL doesn't mean schemaless. You can have a schema and be NoSQL, and that is the direction most NoSQL databases are moving into (or have moved into).
> If that's legitimately your opinion on that topic then I suggest you expand your knowledge.
So, If my knowledge were expanded I would think NoSQL is an equally valid option, and not a worse one? I hesitate to do any more expansion because of this panel held in 2014 [0] asking weather we are in a big data bubble, and probably answering "yes", but I wasn't there.
Simple query language is REALLY good too. It has a kind of general usefulness.
> Keep in mind that NoSQL doesn't mean schemaless. You can have a schema and be NoSQL
> So, If my knowledge were expanded I would think NoSQL is an equally valid option, and not a worse one?
For some things NoSQL would be a better option. For most things SQL remains the better option.
> I hesitate to do any more expansion because of this panel held in 2014 [0] asking weather we are in a big data bubble, and probably answering "yes", but I wasn't there.
We were in a dot-com bubble around 97-2000, maybe the internet is a bad idea also?
> Can you also have SQL and be NoSQL?
By definition, no. But some NoSQL databases do support an alternative to SQL with some of SQL's properties (e.g. JSON-like syntax).
According to their website they have 1000s of customers paying 1200+/m. At the low end they're getting 1.2 million in revenue a month and only have 9 employees. Why did they sell? Something is not adding up.
According to the pricing page, Get Satisfaction's only public pricing is the $1,200/mo subscription. ZenDesk starts at $25m/agent for the community solution.
Granted, they are slightly different products; I was just grabbing the nearest competitor I could think of. (They're in the same space, though, and competing directly for the community/knowledge base part of their products.)
Not sure where you're seeing 9 employees. At the end of 2013 they had 40 employees, and while they laid 10% off in early 2014, they still had over 30 a year ago. Larger customers (of which there weren't 1000's) were paying much more than $1200/year, too. But still, the money coming in wasn't anywhere near the burn rate.
There were more than 9 employees at GS - about 40. There's only 9 employees / former employees that have CrunchBase accounts, so that's why you're seeing that number.
It is a necessary evil in my opinion. Typing code perfectly without the aid of code completion reinforces the idea that attention to detail in coding is extremely important. Furthermore, it forces the user to read every letter which is very important when first starting out.
"Texting while driving reinforces the idea that you need to pay attention to many different things while driving, which is extremely important. Every new driver should text constantly while driving, or else they will never become good drivers."
