I have an MIS degree, and generally, you're correct. They're light on technology, though I did learn some basics. I already knew a lot of that already, though... what I learned the most from were the Accounting, Marketing, and Business Management classes I took.
Personally, I always use either an auto-incremented ID or a GUID. I don't like using a real value of the object as a key. Generally, I think it's good practice, but you're right... I'd index off of that.
I grew up in Memphis. Prince Mongo had a nightclub that was the place to go for high school kids. They apparently never checked for ID's... it was known for serving to high schoolers.
And, Apple and Microsoft have previously funded patent trolls (IV). And IBM has more than 50,000 patents and brings in over $1 billion annually in licensing revenue.
It's a bit difficult where I am (semi-rural)... busy roads, no sidewalks, dogs without leashes (pitbull attacks are too frequent).
But, I do the same with running. I drive to nearby trails most every day. And for the family, we do short backpacking trips with no real goal. Just hike a few miles out to a campsite, hang out, read, cook, play around, and then head home the next evening. My kids are young (7 and 12), and I think it does them a lot of good to be able to cover some distance and pack things in and out on their own.
Exactly. And I think it's a potentially valid argument (without knowing all the details about the case). But, not knowing about a patent, or saying you didn't copy from a non-existent (or existing) implementation of it, doesn't mean you're not bound by it.
Let's say I patent a design for a table, something unique and interesting that's never been done before. Unfortunately, I haven't gotten around to building it yet, or haven't marketed it publicly. You come around after my patent and build and sell a table that is very similar to my table design... even exactly the same in some respects. Even though you may not have known about my patent, and didn't maliciously copy anything, you would still be infringing upon my patent. Even if you just built the table from someone else's parts.
The resolution would be that you either pay me a reasonable license fee, buy the patent, or argue over the validity. For the validity aspect, you either say you had prior art that predates my table design, that some other prior design existed, or that my patent shouldn't have been granted for some other reason.
I worked for a company that invented a novel product but didn't patent it. Some other company came around and made the same thing a few years later and patented it. Personally, I think they knew about our product, but that's not important. They were granted the patent and then proceeded to send warning letters to our customers, saying they were the patent holders and might be calling later to collect license fees. Then, they sent something to us saying, hey, we can proceed with collecting from your customers, or you can license it from us directly and it'll cover all your customers.
We could have gone to court to have the patent invalidated. We had prior art. But, not knowing what prior art they had, and the generally slow nature of that process, and the risk to our customers, we just paid them. It was an annual fee that wasn't too onerous and made it worth it just to pay it.
That is about the trolliest of patent trolling. But, they played their hand perfectly and make a lot of money on that license annually with no real work to get it.
Personally, I think software and process patents shouldn't exist.
I guess I don't understand the significant advantage this would provide. You can accomplish some of the same functionality with other control flow libraries. Also, I could see the future declaration, with potentially cascading effects, causing as much confusion in the code as callbacks.
I just see it as removing a layer of complexity... I don't really care for having PayPal functionality, and not having to worry about the monthly fee paid to you makes it easier on me and you. You get paid quickly, and I don't have to account for another fee. The 50 cents just becomes part of COGS.
Would be nice if they decided that cashflow forecasting (Microsoft Money and Quicken Online both did that well-ish) was important to add. That's the single reason I haven't gone with Mint.
I think the issue comes across pretty clearly in the initial conversations. If you're dealing with a client looking for the cheapest possible website, he's going to force the issue of price early on. If you're dealing with a solution-oriented one, there's some understanding of the cost to value relationship.
To me, that's the key. Value. A $10,000 website is a bargain if it allows them to bring in much more than that in new business or save more than that in costs. But to get that message across, you have to quantify and drive home the potential payoff.
I have both RamNode and Digital Ocean servers in production.
In terms of performance and cost, both are great. I haven't ever had any issues with Digital Ocean. With RamNode, they've had a couple of issues where there's been minimal downtime. And they had a breach back in June, but responded well.
I think I trust Digital Ocean more. The setup is easier and performance maybe slightly better.
I had to re-do our TeamCity integration when they stripped out the IIS Path property out of the project file in favor of publishing profiles. For a shop like ours, where we have lots of small projects, automating the deployment is pretty critical. I don't want to have to add 120 publish profiles when previously I could rely on the project settings.
Ultimately, we hacked together a fix, but I'm still wary of their changes.
Obviously that's not sustainable... but even the 60 hour version sounds pretty rough to me. Without a wife and kids, maybe. But I think if I tried this I wouldn't have to worry about a wife and kids anymore.
Am I the only one who works better and more efficiently when I have a little bit of a break in between?