22,030 reputation
14486
bio website thehungersite.com
location United Kingdom
age 46
visits member for 3 years, 9 months
seen 11 hours ago
experienced software engineer with many years in the industry, mostly c++ for large-scale, high-reliability systems.

Oct
21
awarded  Revival
Oct
19
awarded  java
Oct
18
answered Java Desktop Application Requirement - Is sockets the preferred choice ?
Oct
17
answered Architecture guidelines for a “single page web-app”
Oct
16
comment When does one hard-code actual data values into the code as opposed to using a DB?
@Dunk a ini file was a suggestion for the truly simplistic config files, anything greater than that is best served by an embedded SQL DB - SQLite is awesome, or Microsoft's LocalDB for example. XML might be a middle-ground, but I often see them turn into monsters, and you still have to write some parsing code for an XML schema, especially when you start to nest those elements.
Oct
16
comment When does one hard-code actual data values into the code as opposed to using a DB?
@mcottle nothingis a substitute for organisation. I worked at a place that would update the DB directly... and no-one quite knew what half the data in there meant after time. How do you deal with script-based input data? By dropping the DB and running the scripts to populate the test DB every time you release a new version. Its not difficult to keep on top of changes in there, especially if you have SCM history to tell you whats changed. And seriously, its much easier than having to do the same thing with data stored in XML files!
Oct
16
comment When does one hard-code actual data values into the code as opposed to using a DB?
@mcottle fixed data entered into your RDBMS can be stored as a SQL script of insert statements. This can happily be version controlled. too. Frankly, if you need a single local file for config, you should be considering SQLite anyway. A XML config file is always a worse choice than a really simple "ini" file for simple stuff, or a DB for more complex stuff.
Oct
14
awarded  project-management
Oct
13
answered How should I break this user story into tasks
Oct
13
comment How do you solve issue of consistency in concurrent and distributed application (built around Bankers Dilemma)?
The same way - if you cannot lock all participants (and many times you cannot) then you need a reciprocating system such as this. Obviously it depends on your data, systems and access mechanisms. For example- move file, you can move the file to destination and then delete the original - but if you cannot delete the original after copying you can delete the destination. Many file systems do similar - changes go to cache, and a log. If your drive crashes before the cache is flushed the log is used to ensure file consistency by writing the changes or dropping them (eg compare FAT v NTFS).
Oct
13
answered Create fake HTTP server to simulate an API for testing
Oct
13
answered How do you solve issue of consistency in concurrent and distributed application (built around Bankers Dilemma)?
Oct
9
comment Codifying architecture in requirements
If the modules map to hardware modules, then it seems quite reasonable to have these requirements!
Oct
9
comment Codifying architecture in requirements
I'm not sure why the reference to processing power is there then. I suppose you could treat the modules as logical components, not physical ones then. Put the functionality in namespaces regardless of which dll or exe they get built into.
Oct
9
answered Codifying architecture in requirements
Oct
6
awarded  Nice Answer
Oct
6
answered On GitHub, etiquette and pull requests
Oct
6
comment On GitHub, etiquette and pull requests
1. create new github user, fork your own project, make changes, switch to old user, make pull request, switch to new user and see if there's any notification. or... contact github support :)
Oct
6
answered DDD - If an object is saved as a whole to the database, is it per definition an entity, or is it still possible that it is a value object?
Oct
6
comment What should I do in C++ when implementing a container class: storing objects by value or by reference?
don't put raw pointers in containers - especially for a newbie. Stick to shared_ptr or unique_ptr for safety, then the issue becomes one of stack v heap allocation of objects (and yes, prefer stack)