457 karma · joined April 27, 2013
(After a bit of digging, it seems that Basel II puts Legal Risk in the Operational Risk bucket, which is something I tend to agree with... will open a ticket)
What do you think?
Does our discipline lend itself to this kind of rigor, or are all our projects unique software snowflakes?
... I am about to pick an SVG animation tool and I'm not sure which way to go...
Author here. This is a page from the "Risk-First" project, about risk in software projects... trying to catalog different types of risks within software development.
I'd really appreciate some feedback on this subject from this knowledgeable community, cheers!
Feel free to ask anything.
I agree with you that it's nice that our bodies make things _nice_ to eat as well as recognising nasty stuff. I wonder if there is an evolutionary reason for that too...
Sadly, there are still some things that _don't_ taste bad but will kill you... hidden risks of eating I guess.
I talk about Complexity Risk here: https://github.com/risk-first/website/wiki/Complexity-Risk
Often, Complexity is fine, but then something bites you in the ass unexpectedly. Sounds like risk to me.
- https://github.com/risk-first/website/wiki/Communication-Ris... - https://github.com/risk-first/website/wiki/Complexity-Risk#c... - https://github.com/risk-first/website/wiki/Coordination-Risk
Problem is, the context of the project will often involve people of questionable competence...
"Everyone has a plan 'till they get punched in the mouth."
On the one hand, I would like to grow Risk-First as a community, and get other people authoring articles. With this in mind, I am trying to automate the process by which collaborators are added to the github organisation... it's manual at the moment which is already painful.
On the other hand, I wanted to publish this work in order that it could be read off-line (in print form, should be ready end of Feb) or on a kindle (which is currently pre-order). This _probably_ won't generate much income as it essentially is content that is already for free on the website.
Probably, the license is sufficiently permissive that other people could also publish the work as a book for their own means, so long as they retained attribution or copyright notices. I guess this is the usual quandary on making anything open-source.
I expect you're right that the license _should be_ CC-BY. I need to investigate further on this. Do you have any further thoughts on this?
Author here. This is a single page from the larger "Risk-First" project, about risk in software projects.
I put the front page up a week or so ago and it was fairly well-received. Hopefully people will enjoy a festive second-helping.
Feel free to ask anything.
This is a post about defining and understanding the concept of "complexity risk" within software projects.
Hopefully this will be useful and interesting to people here.
Feel free to ask anything and let me know if you think I'm missing anything fundamental.
Cheers
Using plain english is harder than it sounds! :)
Thanks so much for your feedback. Addressing each point in turn:
1. UAT/Integration: this was just an "example process", one that you _might_ follow. YMMV and you could get better results doing things in a different order or with extra steps. The point was to show that each step on your process (whatever it is) is meeting reality and managing risk. I'm with you on this: you should _totally_ prepare for UAT ahead of doing it, because that preparation actually manages risk too - the risk of the users not knowing what to test, or not being available, or not understanding the functionality, or the data not being right etc.
2. On "Do the simplest thing... and refactor": this (and YAGNI) are great "rules of thumb" about how to develop. What I'm trying to do here is explain _why_ they are great. That is, explain how they attempt to manage risk on software projects. On the refactoring point, I cover this in a lot more detail in the section on "Complexity risk", which I'd really appreciate your feedback on.
It's here: https://github.com/risk-first/website/wiki/Complexity-Risk
I'll invite you to the project on github too
thanks, Rob
Feel free to ask anything.
thanks
The problem then moved onto being one of _curation_. Companies such as google, facebook, amazon are in the business of providing curation: i.e. taking away the leg-work of what we should attend to.
A de-centralized web doesn't appear to decentralize the problem of curation at all, which means we are going to still end up with centralized curation and the same or similar monopolies on attention that we have now.
If anything, I feel like now I want to read a few more of his books as a mark of respect.
And, you know, because they were excellent
https://creativecommons.org/licenses/
It would be great if we could "standardize away" the whole T&C fiasco.
Why is it that an (already a millionaire) entertainer _needs_ to get a billionaire on his side just to try and get justice done? This is a totally crazy state-of-affairs.
I've been thinking for a while that it would be nice if we could add events to the CSS syntax, something like:
a[desc] { onMouseOver: asideFunction(); }
I _kind_ of worry that this is subverting the purpose of the css, but since it also handles hover and selected behaviour, it seems like the line isn't well-drawn anyway as to where styling ends and where behaviour begins.
What do other people think?
Lovely comment, and so true. And you're right: for a POC it's unstoppable. I was trying to get to the nub of "why is it perfect for a POC, but not for running an enterprise application"? That's kind of my point, though I admit it was a bit clunkily-put.
In the Clojure world, (and indeed in Haskell and other pure-fp languages) there is a lot more garbage collection. Rich Hickey makes a great case for this trade off here [2].
On the JVM now very little of it is stop-the-world GC, it mostly does incremental. It's been a while since I profiled a Java app in anger, but even back on JDK5 this was the case, and I know they changed it significantly in JDK7 to the G1 collector.. anyone have a clue about that?
[1] https://github.com/robmoffat/pure4j/blob/master/docs/tutoria... [2] http://www.infoq.com/presentations/Value-Values [3] http://www.oracle.com/webfolder/technetwork/tutorials/obe/ja...
But yes, I think this is a workable idea - so long as there was some way of identifying 3rd-party code purity instead of the annotation.