1,936 reputation
513
bio website apokalypsesoftware.com
location Crawfordville, FL
age 50
visits member for 3 years, 11 months
seen Aug 11 at 18:49

Seer. Founder/Pres, Apokalypse Software Corp., Publisher of Productivity Software.


Jan
7
comment KPI's for Programmers
Programmers are Michelangelos? Really? Our work is judged primarily on an aesthetic basis, and not for its performance by a logical calculating machine? In fact our work should be calculating machines: finite-state machines which are nested to varying degrees to produce work in a deterministic order. It is on that basis that KPIs should be determined: how decoupled your FSMs are, and how well integrated they still are to produce the desired work. Craftsmanship is a silly romanticization to justify a lack of engineering discipline.
Jan
6
comment What non-programming books should a programmer read to help develop programming/thinking skills?
Actually, two of the book's authors, Max Jacobson and Murray Silverstein, worked with Christopher Alexander (and others) to assemble those patterns. But again, while APL focused on the patterns to be implemented in a residential structure, this book focuses on patterns for designing/judging a well-designed home. It gives remarkable insight into determining how to design a software system well, or if it was designed so.
Jan
6
comment KPI's for Programmers
@CraigTP - and payment usually comes after the fact as well. Shouldn't there be some metrics to determine whether you were paid fairly and the client got value for the work done? Just as there should be metrics to determine what parts of a codebase are unsound and need of repair before new features are added so it can be determined what developers have been doing with their time or if repairs are warranted or the code should be replaced. Most of the fears expressed here are that metrics will be misused, but if we fail to define proper metrics bad ones are all we'll get.
Nov
30
comment Should one use pseudocode before actual coding?
@Michael, flowcharts are fine for thinking through processes at three different design stages: 1) use cases of how the user and execution environment interact with the processes (ignoring internal mechanics); 2) the internal mechanics of how the processes function; and 3) the process used to develop the software solution. However, because flowcharts provide procedural semantics (eg, conditionals), it's too easy for designers to expose low-level details into the design too early. For that reason I prefer starting with post-it flags, then state diagrams, during analysis & design.
Oct
28
revised What design pattern is best suitable with this context?
added 2 characters in body
Oct
26
revised “Overtime is part of the job” true but a bad attitude?
edited tags
Oct
25
comment How do you portray to non programmers what programming involves?
@John, the issue isn't what brought about the need to explain programming. The fact is that it's yet another variation on the same "explaining programming" theme, and doesn't add enough to the topic to deserve being a separate question.
Oct
25
answered Code duplication with no obvious abstraction
Oct
25
revised Code duplication with no obvious abstraction
edited tags
Oct
25
revised Code duplication with no obvious abstraction
edited tags
Oct
23
revised Does making source code available affect your ability to generate revenue?
edited tags
Oct
23
revised What licence should I choose for my project?
edited tags
Oct
23
revised What are the Pros and Cons of the GPL?
edited tags
Oct
23
revised What are the Pros and Cons of the GPL?
edited tags
Oct
23
revised License requirements for including open source software
edited tags
Oct
23
revised Can a developer get a discount for Microsoft products?
edited tags
Oct
23
revised Ethics, Clients, and legal repercussions
Retagged
Oct
23
revised AGPL-compatible license
edited tags
Oct
23
revised AGPL-compatible license
edited tags
Oct
23
revised Choosing a licence for open source projects
edited tags