Reputation
3,570
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
11 28
Impact
~265k people reached

  • 0 posts edited
  • 3 helpful flags
  • 49 votes cast
Jul
14
comment Dangers of huge monolithic application
Thanks - no "best practices to be followed/sacrificed" and "weighting potential benefits vs potential disadvantages" entries are ever as helpful as someone with first-hand experience from the other side of the fence.
Jul
14
awarded  Scholar
Jul
14
accepted Dangers of huge monolithic application
Jul
14
answered Advantages and Disadvantages of Forced Code Reformat
Jul
14
awarded  Nice Answer
Jul
14
comment Posting High Salary in Job Ad for Programmer
If you want to weed out unskilled people, start off with one decent, deeply tech question in this specific domain - asked even over the phone, before inviting for the interview. Something an expert in the field will get right away, non-expert will fumble with. Never assume people who don't understand half of the words in the ad's requirements section will weed out themselves.
Jul
14
comment Why is using 'final' on a class really so bad?
@Konrad: Except final should denote "No subclass of this class should ever be created" (for legal reasons or something), not "this class currently has no children, so I'm still safe to mess with its protected members". The intent of final is the very antithesis of "freely editable", and a final class shouldn't even have any protected members!
Jul
14
answered Can Agile software development be used in projects defined by a contract?
Jul
14
answered Is it beneficial to have a long-term experience in a specific technology rather than short-term multiple ones?
Jul
14
comment What to explain when asked “How did you implement MVC”?
Why don't you explain it to us the way you would to the interviewer and we then tell if it's ok? I know how I implemented MVC, but how did you?
Jul
14
awarded  Citizen Patrol
Jul
13
comment Do variable names affect the performance of websites?
and if you care about performance so much that you consider shortening variable names to gain a few cycles, not using op-code cache would be criminal... and switching to a compiled language like C would be recommended.
Jul
13
comment Dangers of huge monolithic application
@rwong: 1. The device is stopped for upgrades. While it would survive updates on the fly, we don't want any unexpected results in case update goes wrong for any reason. 2. Single-core ARM9 with embedded Linux. There's a second, supervising CPU running without OS, verifying the main CPU produces sane output.
Jul
13
awarded  Nice Question
Jul
13
comment Dangers of huge monolithic application
@Maxpm: Luckily, our app doesn't drive sunrises and sunsets. We trust Princess Celestia won't fail at her job.
Jul
13
comment Dangers of huge monolithic application
But that applies to both possible architectures...
Jul
13
awarded  Student
Jul
13
asked Dangers of huge monolithic application
Jul
13
comment Too much version control and bug tracking overhead per change?
@maple: One thing is getting made redundant. Another is if people died because of a small typo of yours and on top of losing job you face charges of manslaughter with several years of prison. THIS is what I call mission-critical, and there aren't many pieces of software where you face such risk.
Jul
13
comment How do you answer “explain current architecture of your project” question in interviews?
Sorry but that is currently covered by NDA. Would my previous projects be satisfactory?