847 karma · joined October 4, 2010
In my opinion the value in testing is verifying what an interface should do, not how it does it.
Low density code that doesn't provide application logic is one of my pet peeves.
There is a philosophy that started in the 90s (and Microsoft was proponent of it [1]) that adding more layers to an application would make it more malleable, but in a typical CRUD web app, layers only bloat the code and make it slower.
I'd suspect adding a wrapper to a date class just for the sake of testing is more likely to add bugs than remove them.
[1] http://www.asp.net/web-forms/tutorials/data-access/introduct...
The work was extraordinarily tedious, error prone, yet business critical. We had to keep shimming in new parts of the system, while keeping the old system afloat. While the system was always on the verge of imploding, from the outside, it basically appeared to work, which kept the project chronically understaffed.
I have a lot respect for anyone who aggregates time critical production data from different sources. The nature of the work makes it extremely stressful, yet surprisingly easy for outsiders to underestimate.
I think WealthFront is another good example of the difficulty. I like the direction they are going, but they had to pivot many times to get to were they are now, and they are still a fraction of the size of established players in the market. It still isn't clear if their business model is going to work.
With that said, the inefficiency in the money management business is pretty ridiculous. I think companies built from the ground up on new technology will eventually replace existing players in the market, but the margins will probably be a lot less as well.
Computer Science: Fixed programs, transient data
Data Science: Fixed data, transient programs
BTW, from my link: "If you need to write multiple buffers that are currently in memory you should prefer the gather function writev() before considering TCP_CORK with multiple calls to write()."
I did quite a bit of public speaking in the past couple years and it gets easier over time. I think the best advice is prepare, prepare, prepare.
There is a lot of genius in the article and references, but I will say from experience it is very easy to implement these approaches incorrectly, so unless an application requires the performance benefits provided, it is probably still a better bet to use standard locking mechanisms.
BTW, another product like this is range hoods.
I'm impressed that you tried to break into this business. I thought the existing companies would have it tied up because of their distribution channels. I did look at latex mattresses at the time, but they were an expensive niche. About the only viable alternative to the traditional mattress industry were the foam mattresses being produced overseas.
"I wanted to avoid using buiulding (sic) material that tries to look like something it isn't, but with the siding I had no choice: ALL siding materials I can buy try to look like wood! So, unfortunately, my house is wrapped in faked wood. It doesn't look too bad, but I would have preferred something different."
This drives me nuts as a home owner. I don't mind using synthetic materials in my house, but why are are they all skeuomorphic?
Plus I love the way the house is framed with bricks and mortar. I wish more houses were still built like this in the US, but I suspect that labor would make it cost prohibitive.
We have occasional hiccups in San Jose, but mostly it works pretty smoothly. I've worked in Playa Hermosa and had no problems.
BTW, if anyone is considering developers in Costa Rica, send me an email.
The contractors thought it was pretty strange to have to deal with someone in a different state, but it worked out pretty well. Our culture (at least here in the US) doesn't appreciate outsourcing day to day tasks (and I felt embarrassed telling people I had an assistant). Maybe this comes from our Protestant roots.
It reminds me of an episode of Garrison Keillor's Prairie Home Companion. Some of his characters from Minnesota visit California and find out one of their relatives has a gardener, and they ask if the relative is having any health issues, because they couldn't imagine having someone do their gardening for them, unless they were severely ill.
Update: The poster above mentions getting what you pay for if you pay $2 per hour in the Philippines for instance. I agree with this. I payed significantly more, but I feel as though I got my money's worth. It isn't that expensive to hire in the US if you look to lower cost areas like the Mid-west.
For this project, I felt it was worth it to have someone who understood the problems of hiring and managing contractors in the US. The person I hired was a homeowner, understood what I wanted to accomplish, and did an awesome job. It turned out to be a fraction of the cost of the overall project, and was money well spent.
What I did was start with a small project, and verify the developer's work. This is much easier to do if you are technical.
If you are non-technical, I think these sites are worthless. There is no way to know what you are getting.
Edit: I should say they are worthless for technical work. I've also hired a non-technical assistant who was in the US and that worked out great, and I'm sure other non-technical people could do the same.