Fluentx: A Special .NET Library
Fluentx covers all major C# control statements, and eliminates the limitations within them, and adds more features, the assembly holds 5 major categories: C# control statements, Helper Classes, Extension Methods, Specifications Pattern, Object to Object Mapper, the assembly will get bigger and bigger by time as we will add more and more to it to make it used and helps everybody out there. It also has an implementation of Specification Pattern as a validation for any type of code, whether its a business validation or anything.
Leaders in Lean Software Knowledge
The primary thing that we are advocating is not to think of software development as coding and testing. Rather to think of it as figuring out what is worth doing, what’s going to delight the customer, doing it, making sure it’s working well, getting it in service to the customer, and getting feedback from the customer. The really important metric is how fast you can get feedback from a customer about the actual, deliverable application that you are creating. That is beyond the realm of most people who are thinking about software all by itself. It gets toward the devops on one end, and it gets toward the design thinking on the front end.
CAPEX Deferred Eventually Makes the Company Sick
The constant deferral of CAPEX has the real potential to make your company sick. Investments in computers, machines, plants, equipment, buildings and more are the backbone of a company. When CAPEX is intentionally constrained in favor of parking cash for a rainy day or buying back stock (at already high prices), much needed upgrades are deferred. Worse, constant deferrals of capital upgrades are like a “hidden tax” in that by not spending cash on upgrading creaking systems and infrastructure, it’s highly likely something much worse can happen down the road (i.e. the millions extra Los Angeles has to spend just to clean up the messes resulting from infrastructure failures).
Fighting fraud in banking with big data and analytics
Current systems often cannot handle the volume, frequency or the complexity of today’s fraud activity. Also many banks have, over time, cobbled together numerous fraud point solutions, making a holistic view of threats impossible. The old model of responding to attacks and fraud well after the fact just won’t work in today’s world of sophisticated and organized financial crimes. Adding to the problem, banks have created a corporate silo mentality that’s often a barrier to successfully fighting fraud. As a result, too many organizations remain vulnerable to fraud because they aren’t taking advantage of new capabilities to fight these threats.
Need for Speed: Parallelizing Corporate Data
A critical success factor is enabling iterative, variable, and transparent results tuned to the personal and organizational work tempo of analysts, managers, and business product delivery. In almost all mission-critical activities, the specific requirements of the business on the data environment are neither static nor known at a level of detail sufficient to supply traditional tools and methods. This leads to the accursed business-technical organizational chasm. - See more at: http://vision.cloudera.com/need-for-speed-parallelizing-corporate-data/#sthash.LzlvfqiA.dpuf
5 tips for keeping IT projects on track
After more than 20 years managing IT projects at global enterprises, I have seen and experienced many situations. I’ve celebrated many successes and also faced many challenges. Some of these experiences have served as good examples of what works and what doesn’t in IT project management. Now I am putting these lessons to work in my current role as chief technology risk officer at GE Capital. My job includes oversight of our IT investments, making sure our largest-scale IT projects stay on track and remain strategic to our business. Based on this broad set of experience, here are five key lessons that have proven particularly useful:
SQL Server unit testing framework
This unit test framework has no dependencies beyond SQL server and does not rely on the common language runtime. The tables and functions in the downloadable source files (.sql) should ideally be created in a separate database on the server that hosts the databases being tested. The process will be familiar to anyone who has used the unit test frameworks such a NUnit, MSTest etc. First you set up the prerequisites for the test (pre test setup) then you perform the assertion (unit test) then you clean up anything created by the unit test (tear down).
Shellshock: How to protect your Unix, Linux and Mac servers
A more serious problem is faced by devices that use embedded Linux — such as routers, switches, and appliances. If you're running an older, no longer supported model, it may be close to impossible to patch it and will likely be vulnerable to attacks. If that's the case, you should replace as soon as possible. The real and present danger is for servers. According to the National Institute of Standards (NIST),Shellshock scores a perfect 10 for potential impact and exploitability.
Freaky Data Science
Practical freak advice pertinent for data science includes focus on solving small problems, being wary of “moral” solutions to practical problems, acknowledging what you don't know – “Everyone's entitled to their own opinion but not to their own facts” – and being cognizant of when it's time to quit. And of course the gold standard of determining truth for freaks is the randomized experiment “The impulse to investigate can only be set free if you stop pretending to know answers that you don't.” Perhaps no chapter has more to offer the budding data scientist than “How to Persuade People Who Don't Want to Be Persuaded”.
Take Aways from the Reifer 2014 Quantitative Analysis of Agile Methods Study
Reifer Consultants LLC recently published a benchmarking report that compared the productivity, cost and quality performance achieved by software development projects that use agile methods against similar ones that employ traditional, plan-driven approaches. The results of the analysis were based on 1,500 projects, 500 of which employed a variety of agile methods, over a ten year period using data supplied by 100 organizations. This condensed white paper summarizes seven ‘trends and take-aways’ taken from our report entitled “Quantitative Analysis of Agile Methods1.”
Quote for the day:
"There are many elements to a campaign. Leadership is number one. Everything else is number two." -- Bertolt Brecht
Fluentx covers all major C# control statements, and eliminates the limitations within them, and adds more features, the assembly holds 5 major categories: C# control statements, Helper Classes, Extension Methods, Specifications Pattern, Object to Object Mapper, the assembly will get bigger and bigger by time as we will add more and more to it to make it used and helps everybody out there. It also has an implementation of Specification Pattern as a validation for any type of code, whether its a business validation or anything.
The primary thing that we are advocating is not to think of software development as coding and testing. Rather to think of it as figuring out what is worth doing, what’s going to delight the customer, doing it, making sure it’s working well, getting it in service to the customer, and getting feedback from the customer. The really important metric is how fast you can get feedback from a customer about the actual, deliverable application that you are creating. That is beyond the realm of most people who are thinking about software all by itself. It gets toward the devops on one end, and it gets toward the design thinking on the front end.
CAPEX Deferred Eventually Makes the Company Sick
The constant deferral of CAPEX has the real potential to make your company sick. Investments in computers, machines, plants, equipment, buildings and more are the backbone of a company. When CAPEX is intentionally constrained in favor of parking cash for a rainy day or buying back stock (at already high prices), much needed upgrades are deferred. Worse, constant deferrals of capital upgrades are like a “hidden tax” in that by not spending cash on upgrading creaking systems and infrastructure, it’s highly likely something much worse can happen down the road (i.e. the millions extra Los Angeles has to spend just to clean up the messes resulting from infrastructure failures).
Fighting fraud in banking with big data and analytics
Current systems often cannot handle the volume, frequency or the complexity of today’s fraud activity. Also many banks have, over time, cobbled together numerous fraud point solutions, making a holistic view of threats impossible. The old model of responding to attacks and fraud well after the fact just won’t work in today’s world of sophisticated and organized financial crimes. Adding to the problem, banks have created a corporate silo mentality that’s often a barrier to successfully fighting fraud. As a result, too many organizations remain vulnerable to fraud because they aren’t taking advantage of new capabilities to fight these threats.
Need for Speed: Parallelizing Corporate Data
A critical success factor is enabling iterative, variable, and transparent results tuned to the personal and organizational work tempo of analysts, managers, and business product delivery. In almost all mission-critical activities, the specific requirements of the business on the data environment are neither static nor known at a level of detail sufficient to supply traditional tools and methods. This leads to the accursed business-technical organizational chasm. - See more at: http://vision.cloudera.com/need-for-speed-parallelizing-corporate-data/#sthash.LzlvfqiA.dpuf
5 tips for keeping IT projects on track
After more than 20 years managing IT projects at global enterprises, I have seen and experienced many situations. I’ve celebrated many successes and also faced many challenges. Some of these experiences have served as good examples of what works and what doesn’t in IT project management. Now I am putting these lessons to work in my current role as chief technology risk officer at GE Capital. My job includes oversight of our IT investments, making sure our largest-scale IT projects stay on track and remain strategic to our business. Based on this broad set of experience, here are five key lessons that have proven particularly useful:
SQL Server unit testing framework
This unit test framework has no dependencies beyond SQL server and does not rely on the common language runtime. The tables and functions in the downloadable source files (.sql) should ideally be created in a separate database on the server that hosts the databases being tested. The process will be familiar to anyone who has used the unit test frameworks such a NUnit, MSTest etc. First you set up the prerequisites for the test (pre test setup) then you perform the assertion (unit test) then you clean up anything created by the unit test (tear down).
Shellshock: How to protect your Unix, Linux and Mac servers
A more serious problem is faced by devices that use embedded Linux — such as routers, switches, and appliances. If you're running an older, no longer supported model, it may be close to impossible to patch it and will likely be vulnerable to attacks. If that's the case, you should replace as soon as possible. The real and present danger is for servers. According to the National Institute of Standards (NIST),Shellshock scores a perfect 10 for potential impact and exploitability.
Freaky Data Science
Practical freak advice pertinent for data science includes focus on solving small problems, being wary of “moral” solutions to practical problems, acknowledging what you don't know – “Everyone's entitled to their own opinion but not to their own facts” – and being cognizant of when it's time to quit. And of course the gold standard of determining truth for freaks is the randomized experiment “The impulse to investigate can only be set free if you stop pretending to know answers that you don't.” Perhaps no chapter has more to offer the budding data scientist than “How to Persuade People Who Don't Want to Be Persuaded”.
Take Aways from the Reifer 2014 Quantitative Analysis of Agile Methods Study
Reifer Consultants LLC recently published a benchmarking report that compared the productivity, cost and quality performance achieved by software development projects that use agile methods against similar ones that employ traditional, plan-driven approaches. The results of the analysis were based on 1,500 projects, 500 of which employed a variety of agile methods, over a ten year period using data supplied by 100 organizations. This condensed white paper summarizes seven ‘trends and take-aways’ taken from our report entitled “Quantitative Analysis of Agile Methods1.”
Quote for the day:
"There are many elements to a campaign. Leadership is number one. Everything else is number two." -- Bertolt Brecht
No comments:
Post a Comment