244 reputation
15
bio website
location
age
visits member for 2 years, 6 months
seen Dec 6 '13 at 10:07

Dec
6
answered How can I automate production deployments without experiencing extreme anxiety?
Dec
6
comment How do you update your production codebase/database schema without causing downtime?
Well, I'm afraid you show your ignorance once more, as covering indexes are just one of the many ways to handle performance problems, and they're far from the best or universal solution, as they resemble a half-assed write-through cache that costs you some serious write performance. Not a fan.
Nov
29
comment How do you update your production codebase/database schema without causing downtime?
I wonder what RDBMS you used to have select * exhibit performance problems. Criticizing an approach you do not understand is surely not the way for you to improve ;)
Nov
20
comment How do you update your production codebase/database schema without causing downtime?
Yes really, there is no added security in avoiding select *. It has nothing to do with strongly typed languages and everything to do with very bad design. If your framework cannot handle change seamlessly, it's useless. When I change a column, my application never stops working. When you do it breaks. I don't think there's any question as to which one is more reliable or secure.
Nov
18
comment How do you update your production codebase/database schema without causing downtime?
Actually, for forward planning and adaptability, select * from is infinitely better than listing columns manually. Using explicit column names results in a lot of technical debt in most cases. If your code breaks from new columns, your code is already broken.
Oct
18
comment What will be correct answer to “why is NoSQL faster than SQL” on interview?
That's bull. The relational model covers everything you can make in NoSQL and so much more. The only advantage of NoSQL is that a simple and inconsistent approach to scaling is built in and easy to use. It has nothing to do with SQL, and everything to do with not caring about ACID properties. You can have sync jobs between independent SQL nodes that will have exactly the same (very bad) scaling and consistency properties the NoSQL stores have. The difference is that SQL nodes can ALSO have consistency if you choose to.
Oct
17
comment What will be correct answer to “why is NoSQL faster than SQL” on interview?
This, by the way can be realized with simple materialized view, or a cache layer, while still benefiting from all the SQL goodness. Anything properly modeled is relational, and logical data duplication is not a solution (the mat. view is a duplication but not a logical duplication because it is simply an image of something else).
Oct
11
comment How can I make sure that I'm actually learning how to program rather than simply learning the details of a language?
whatever. content > form . keep your form, I'll keep my content.
Oct
11
comment How can I make sure that I'm actually learning how to program rather than simply learning the details of a language?
@gnat do whatever you like. I'm just telling you that since most programmers can't code for shit, their feedback is potentially harmful, and you should be bringing bags and bags of salt to deal with that. Also I believe "editable and readable by morons" is not a sign of quality at all. Believe what you want but don't go around -1 just because people don't agree with your vision.
Oct
11
comment Overcoming slow problem solving due to increased knowledge of what might go wrong
I think the only answer is to find customers willing to pay for the quality you want to deliver. I haven't found them yet. Since I'd rather die than waste my life producing crap, I'm currently offering all that quality for free. Unlike you though, I'm still incredibly fast because I picked the right approach to software development and fully capitalize on all past work.
Oct
11
comment Overcoming slow problem solving due to increased knowledge of what might go wrong
@RhysW A program can be mathematically 100% correct, it's not that hard. What's hard is working around all the bugs in the software that you didn't write but have to work with.
Oct
11
comment Overcoming slow problem solving due to increased knowledge of what might go wrong
This answer is bullshit. Go on, go try and tell a potential client that you will do it for 40K instead of 20K but with 10x more quality and reliability. They will tell you this: "My budget is 20K and I don't need that quality". At some point you have to accept that 99% of clients don't really care about quality, and any quality there is will be your personal investment.
Oct
11
comment Overcoming slow problem solving due to increased knowledge of what might go wrong
Actually you just took the example of the worst: web software, where php noobs are officially competition. Price is an extremely important factor, and when I deliver high quality software, my clients pay for the software and I pay for the high quality.
Oct
11
answered Overcoming slow problem solving due to increased knowledge of what might go wrong
Oct
11
comment How can I make sure that I'm actually learning how to program rather than simply learning the details of a language?
Actually this is exactly why you shouldn't learn OO first, as this formats your brain with one of the worst AST imaginable.
Oct
11
answered How can I make sure that I'm actually learning how to program rather than simply learning the details of a language?
Oct
11
comment How can I make sure that I'm actually learning how to program rather than simply learning the details of a language?
My strategy has always been to focus on pure skills rather than specific skills.
Sep
30
revised What's the benefit of object-oriented programming over procedural programming?
added 4 characters in body
Sep
28
awarded  Editor
Sep
28
revised What's the benefit of object-oriented programming over procedural programming?
added 35 characters in body