Reputation
21,047
Next tag badge:
83/100 score
19/20 answers
Badges
6 41 113
Impact
~787k people reached

Jun
6
comment Is there a source for user opinions on commercial enterprise software?
In case you were living under a rock for the past 20 years let me clue you in, this is the Modus Operandi of the industry. A big portion of the industry and a LOT of software jobs are riding on these large enterprise software suites. Sometimes it was a poor choice, other times there is a LOT of money to spend and they WANT IT based on the name recognition alone. Appearances drive the industry and a lot of times people make money and obtain investment capital by spending BIG on cumbersome enterprise software suites and unnecessarily large development teams.
Jun
6
answered What's the rationale of not simply disclosing the license fees for a commercial libary or tool?
Jun
5
answered Alternative for Access+SQL Server for enterprise projects
Jun
2
comment Prototyping vs. Clean Code at the early stages
+1 Great Post! I would add that while it may seem useless after you have developed that feature, NEVER throw away your prototypes. I always source control every prototype I work on because sometimes I refer back to them for tips and hints.
Jun
2
comment Is there any hope for writing good code atop a horribly designed database?
@John, This is good that they RECOGNIZE the need for refactoring. It is a sign of good long term management and the first step to actually refactoring.
Jun
2
comment Is there any hope for writing good code atop a horribly designed database?
+1, This can be a good idea too as long as all application data access code is properly separated from other layers, and that data access code can be refactored to work with the new schema
Jun
2
comment Is there any hope for writing good code atop a horribly designed database?
+1 @HLGEM, These are good points. Your advice is sound if the application code is well designed. Refactoring in parts is probably the best way to go but in my entire career I have never seen that work successfully. It may have been because of poor project management however, not because it is an unsound idea.
Jun
2
comment Is there any hope for writing good code atop a horribly designed database?
As I have commented to others making this suggestion, it is a good suggestion but it is highly likely that if the database design is crap then the application code is likely crap as well. I don't see the point of going to this trouble if the application code should be refactored as well.
Jun
2
comment Is there any hope for writing good code atop a horribly designed database?
This is all well and good but I have the strong suspicion that if the database design is a mess then the application code is probably worthless too.
Jun
2
answered Is there any hope for writing good code atop a horribly designed database?
Jun
2
comment How can we make agile enjoyable for developers that like to personally, independently own large chunks from start to finish
If you are going to do that with a few people then just pay attention to how it affects the morale of others who are actually doing project work. They may feel you are giving special advantage or preferential treatment to people who complain.
Jun
1
answered How can we make agile enjoyable for developers that like to personally, independently own large chunks from start to finish
Jun
1
comment Should you ever release something that you yourself could hack?
+1 For context, I would add that any data which includes social security numbers, identification numbers, or credit card numbers should also have attention to security. Systems that don't store any of this information and are not critical systems have low risk data and you wouldn't need to worry about security as much.
May
31
comment Should you ever release something that you yourself could hack?
No guarantee? Why don't you tell that to the millions of Sony customers who had their social security numbers and other sensitive data stolen because of EXACTLY such security holes as the OP is suggesting.
May
31
comment Should you ever release something that you yourself could hack?
+1 for DOCUMENT EVERYTHING!!! When a major disaster occurs and the manager's job is on the line, he/she will do ANYTHING to shift blame in ANY way they can. If you document issues, emails, notifications, memos and other documentation related to the decision then you are protecting yourself from a bad situation.
May
31
answered Should you ever release something that you yourself could hack?
May
31
answered Best practice to save data in different databases using C# ADO.NET
May
31
answered What's your suggestion if the company didn't recognize my contribution towards a big project?
May
31
answered Long-Term Strategy For Implementing a QA System?
May
31
comment Any tips how to successfully job hunt?
@Ian, Yeah the phone calls can be highly annoying. The last time I was laid off I put my resume up on Monster and the next morning I woke up at around 9am with over 20 voicemails. I just filter out the recruiters I don't know or who have wasted my time in the past and only talk to the ones who have gotten me jobs or interviews.