Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Risk and Assumptions Expand / Collapse
Author
Message
Posted Wednesday, January 21, 2009 2:25 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:29 PM
Points: 32,819, Visits: 14,965
Comments posted to this topic are about the item Risk and Assumptions






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #641165
Posted Wednesday, January 21, 2009 8:17 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 8:23 PM
Points: 36,002, Visits: 30,297
I would be working to lower risk as much as possible. Adopting techniques that you are confident in, learning new skills and then applying them, even in side projects, can help grow your skills, increase the chances of projects being completed that the client is happy with, and keeping you employed. Now is the time to reassess the way you work, and find ways to show that you can work with your clients to meet their needs in an efficient manner.


It's funny... I was just in a heated-debate thread about this very subject. One of my comments was that if you don't want to take the time to learn your own trade well enough to be good at it (ie, write good set based code as quickly as others can write a cursor), then get out of the business.

5 stars, Steve!


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

"Change is inevitable. Change for the better is not." -- 04 August 2013
(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #641343
Posted Thursday, January 22, 2009 2:26 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:29 PM
Points: 32,819, Visits: 14,965
Thanks and hopefully people will see that spending time learning and building skills is worth it.






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #641433
Posted Thursday, January 22, 2009 5:29 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, June 19, 2012 8:27 AM
Points: 29, Visits: 171
I don't agree with this; "Efficient in their eyes, not yours"

This is probably one of the hardest things to do but; both you and the customer must think it's efficient. The customer will not always know what is efficient; which is why you have a job in the first place. You will not win the efficiency battle every time but the times you do will increase the confidence your management has in your team. Making you more valuable.

I do agree that not learning the skills will prove to risky in these times. Not knowing the skills will also make it harder to prove to management your way is more efficient than theirs.
Post #641560
Posted Thursday, January 22, 2009 6:04 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, May 07, 2012 9:23 AM
Points: 304, Visits: 716
"Risk comes from not knowing what you're doing." I think that's true and that's part of the reason we'd had issues in our financial markets over the last couple of years.

Steve, I could not DISAGREE with your premise more... Risk may come from not knowing what you are doing, but the biggest lesson coming from our financial mess is that these people knew exactly what they were doing - they were greedy, and ripping off honest citizens. For example, its very hard for me to imagine that Bernard Madoff did not know very well what he was doing as he unloaded his illegal scheme all over people. And it would be simply mindless to presume that the thousands of mortgage agents writing loans they knew the people could not pay - so they could get their commission - did not know exactly what they were doing.

So though I would respect Mr. Buffet, I would re-tinker the concept: Risk comes from people with low morals and no ethics who have bought into the concept that if they just take care of themselves, the rest of the world will somehow get by. It doesn't, it isn't and we can thank these jerks for our current state of affairs.

To that end, IT people should remember that they serve end-users, not themselves, and thus deliver something they can be proud of, not ashamed of. Pride in your work, and a knowledge that it is a reflection of you as a person, would go a very long way to keeping risk in check.




There's no such thing as dumb questions, only poorly thought-out answers...
Post #641597
Posted Thursday, January 22, 2009 6:26 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:29 PM
Points: 32,819, Visits: 14,965
I do believe there were immoral people involved, people taking advantage of others. Those people exist, and unfortunately they are in plenty of businesses.

However, I have read quite a few things about risk analysis in banks and there were lots of people that built models designed to calculate risk, probabilities of default, etc., and they used this to lower capital requirements and increase leverage. Many people did this with the best of intentions, being more efficient in business, etc, and they should not have been allowed to do so. At least not without more extensive testing across years, perhaps decades.

They thought they were more closely calculating risk, but in fact they had flawed models that didn't take into account the changes at other companies (meaning a larger section of the financial community) and this actually increased their risk.

Or at least I think they are a big part of the problem. Not all of it, but a big part. People ripping off others, or making bad loans knowing they weren't going to hold them is another big part. Plenty of blame to go around.

I still think many people in software increase risk unnecessarily by not learning more about their craft and developing better, perhaps more difficult or harder to learn, techniques to get things done.

I agree that we have to work with clients, and help them understand, but many IT people forget that getting things done, getting what the client needs (not necessarily how they want it done, but the end result should matter) and build what they think works well, or works better instead.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #641620
Posted Thursday, January 22, 2009 6:31 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:12 AM
Points: 10,910, Visits: 12,553
I think the biggest issue is lack of true project management in IT. I know I struggle with taking all the information from users and accurately converting those to requirements and design. A lot of it is in knowing the right questions to ask.



Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2
Post #641630
Posted Thursday, January 22, 2009 6:50 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 3:31 PM
Points: 2,628, Visits: 19,098
In my current environment, it seems that the folks I work with think that we should not have to know the business very well, which could lead to not knowing the right questions to ask. I came up through the business and landed in a pseudo-IT role, so I have the opposite perspective, where I can't understand how you can possibly deliver a valuable product when you don't know how it will be used.

I'm working to try and give the new analysts a basic understanding of the business based on my experience, hoping to improve the results of this cycle, but we shall see.


---------------------------------------------------------
How best to post your question
How to post performance problems
Tally Table:What it is and how it replaces a loop

"stewsterl 80804 (10/16/2009)I guess when you stop and try to understand the solution provided you not only learn, but save yourself some headaches when you need to make any slight changes."
Post #641661
Posted Thursday, January 22, 2009 6:52 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Friday, April 11, 2014 7:06 AM
Points: 482, Visits: 138
I agree that it's always a good idea to learn new skills, apply them, and add more depth to your current skill set, no matter what state the economy is in. But, one important component to the risk of any project is the inability of IT managers and developers to effectively communicate with the business leaders and end users that they are supporting.

I've seen a good deal of bad programming and bad business analysis on software projects -often the final product doesn't support the needs of the business community, and a lot of work is required down stream to clean up the mess. Bugs can be fixed and efficiencies can be found when the problems are a matter of system performance. Adding to your skill set can cut down on these problems and allow you to code more efficiently and save many hours of development effort.

However, I feel that a lack of communication skills and direction for IT projects is even worse. If we don't have a true sense of what the business community wants to accomplish while using our software, we could write the most beautiful and efficient code in the world, and it will still be of absolutely no value.

Post #641665
Posted Thursday, January 22, 2009 7:24 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, October 21, 2013 10:48 AM
Points: 966, Visits: 933
However, I have read quite a few things about risk analysis in banks and there were lots of people that built models designed to calculate risk, probabilities of default, etc., and they used this to lower capital requirements and increase leverage.


One interesting thing I read (written by a quant) was that they built models that showed certain reasults. Then management came in and saw that the results didn't match their expectations, so they had the modelers tweak their models.

One of the biggest problems with the whole thing seems to be that the people making these huge financial decisions don't understand risk but thought they had the math down. See Fooled by Randomness, The Black Swan (both by Taleb), the Misbehavior of Markets (Mandelbrot), or one of the myriad of others talking about how the models just didn't match reality.



Post #641699
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse