EddieAwad.com

A River of Useful or Just Fun Stuff 

SQLSaturday Open for Registration

On the weekend of May 22, 2010, the Portland Development community is coming together in a way never experienced before.

Using the University of Portland campus, SQLSaturday, Portland Code Camp, and Portland Bar Camp are combining and coordinating efforts to bring 800-1000 regional technology professionals together for the opportunity to immerse themselves in seminars, presentations, group exploration, and networking. Participants will be able to engage in their preferred technology, as well as to 'sample' other options

Admittance to this event is free, all costs are covered by donations and sponsorships. Please register soon as seating is limited, and let friends and colleages know about the event.

>> Click here to register.

Portland SQLSaturday is encouraging presentations related to interoperability of any of the SQL platforms, including T-SQL (SQL Server), PostgreSQL, MySQL, and Oracle PL/SQL. Abstracts for Platform specific sessions are also encouraged. The event is scheduled on Saturday May 22, 2010 from 8:00 AM until 10:00 PM.

Most sessions will be one hour and fifteen minutes (1:15), and a few 'deep dive' sessions will be longer (2.5 hours). The  'deep dive' sessions will be scheduled for 7:00 PM (after the snacks and refreshments.) Also, throughout the day, there may be opportunities for 30 minute 'SQL snack' sessions.

>> Click here to submit your presentation abstract.

I encourage all Oracle SQL and PL/SQL enthusiasts living in the Pacific Northwest to present in and/or attend this not-to-be-missed event.

Loading mentions Retweet
Filed under  //   conference   oracle   plsql   portland   sql   sqlsaturday  

Comments [0]

Top 25 Most Dangerous Programming Errors

The 2010 CWE/SANS Top 25 Most Dangerous Programming Errors is a list of the most widespread and critical programming errors that can lead to serious software vulnerabilities. They are often easy to find, and easy to exploit. They are dangerous because they will frequently allow attackers to completely take over the software, steal data, or prevent the software from working at all.

RankScoreIDName
[1] 346 CWE-79 Failure to Preserve Web Page Structure ('Cross-site Scripting')
[2] 330 CWE-89 Improper Sanitization of Special Elements used in an SQL Command ('SQL Injection')
[3] 273 CWE-120 Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
[4] 261 CWE-352 Cross-Site Request Forgery (CSRF)
[5] 219 CWE-285 Improper Access Control (Authorization)
[6] 202 CWE-807 Reliance on Untrusted Inputs in a Security Decision
[7] 197 CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
[8] 194 CWE-434 Unrestricted Upload of File with Dangerous Type
[9] 188 CWE-78 Improper Sanitization of Special Elements used in an OS Command ('OS Command Injection')
[10] 188 CWE-311 Missing Encryption of Sensitive Data
[11] 176 CWE-798 Use of Hard-coded Credentials
[12] 158 CWE-805 Buffer Access with Incorrect Length Value
[13] 157 CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program ('PHP File Inclusion')
[14] 156 CWE-129 Improper Validation of Array Index
[15] 155 CWE-754 Improper Check for Unusual or Exceptional Conditions
[16] 154 CWE-209 Information Exposure Through an Error Message
[17] 154 CWE-190 Integer Overflow or Wraparound
[18] 153 CWE-131 Incorrect Calculation of Buffer Size
[19] 147 CWE-306 Missing Authentication for Critical Function
[20] 146 CWE-494 Download of Code Without Integrity Check
[21] 145 CWE-732 Incorrect Permission Assignment for Critical Resource
[22] 145 CWE-770 Allocation of Resources Without Limits or Throttling
[23] 142 CWE-601 URL Redirection to Untrusted Site ('Open Redirect')
[24] 141 CWE-327 Use of a Broken or Risky Cryptographic Algorithm
[25] 138 CWE-362 Race Condition

 

Loading mentions Retweet
Filed under  //   programming   security  

Comments [0]

Thinking Clearly About Performance (paper)

(download)

Creating high-performance as an attribute of complex software is extremely difficult business for developers, technology administrators, architects, system analysts, and project managers. However, by understanding some fundamental principles, performance problem solving and prevention can be made far simpler and more reliable. This paper describes those principles, linking them together in a coherent journey covering the goals, the terms, the tools, and the decisions that you need to maximize your application’s chance of having a long, productive, high-performance life. Examples in this paper touch upon Oracle experiences, but the scope of the paper is not restricted to Oracle products.

via http://method-r.com/downloads/doc_details/44-thinking-clearly-about-performance

Loading mentions Retweet
Filed under  //   oracle  

Comments [0]

Oracle’s SQL Performance Analyzer White Paper

(download)

The SQL Performance Analyzer offers a comprehensive solution to enable users to forecast and analyze how a system change will impact SQL query plans and run time performance, so they can tune their system before they make the change in production. The SQL Performance Analyzer identifies potential problems that may occur and makes suggestions for avoiding any SQL performance degradation. It provides quantitative estimates of the system’s performance in the new environment with high confidence and performs a comparative analysis of the response time of the SQL workload thus allowing for an easy assessment of the change. In this paper we describe the architecture of the SQL Performance Analyzer, its usage model, and its integration points with other Oracle database components to form an end-to-end change management solution.

Loading mentions Retweet
Filed under  //   oracle   sql  

Comments [2]

Why Oracle Application Express?

Loading mentions Retweet
Filed under  //   apex   oracle  

Comments [0]

11 Critical Conclusions of the Book "Good Calories, Bad Calories"

1. Dietary fat, whether saturated or not, does not cause heart disease.
2. Carbohydrates do, because of their effect on the hormone insulin. The more easily-digestible and refined the carbohydrates and the more fructose they contain, the greater the effect on our health, weight, and well-being.
3. Sugars—sucrose (table sugar) and high fructose corn syrup specifically—are particularly harmful. The glucose in these sugars raises insulin levels; the fructose they contain overloads the liver.
4. Refined carbohydrates, starches, and sugars are also the most likely dietary causes of cancer, Alzheimer’s Disease, and the other common chronic diseases of modern times.
5. Obesity is a disorder of excess fat accumulation, not overeating and not sedentary behavior.
6. Consuming excess calories does not cause us to grow fatter any more than it causes a child to grow taller.
7. Exercise does not make us lose excess fat; it makes us hungry.
8. We get fat because of an imbalance—a disequilibrium—in the hormonal regulation of fat tissue and fat metabolism. More fat is stored in the fat tissue than is mobilized and used for fuel. We become leaner when the hormonal regulation of the fat tissue reverses this imbalance.
9. Insulin is the primary regulator of fat storage. When insulin levels are elevated, we stockpile calories as fat. When insulin levels fall, we release fat from our fat tissue and burn it for fuel.
10. By stimulating insulin secretion, carbohydrates make us fat and ultimately cause obesity. By driving fat accumulation, carbohydrates also increase hunger and decrease the amount of energy we expend in metabolism and physical activity.
11. The fewer carbohydrates we eat, the leaner we will be.

Loading mentions Retweet
Filed under  //   diet   fitness  

Comments [1]

So long, old friend... James Gosling's tribute to Sun

Loading mentions Retweet
Filed under  //   oracle   sun  

Comments [0]

Hone your written communication skills. A few ways to do that:

  • Get a copy of Strunk and White’s Elements of Style. It’s a classic, and gives you the fundamentals you need.
  • Read. Read lots. The more you read good writing, the more your writing will reflect what you absorb. Not sure what good writing is? The more you read, the more you’ll learn.
  • Subscribe to Copyblogger and Men With Pens. Heed their writing guidance.
  • If you’re often confused by some English usage (things like their vs. there, lie vs. lay, or its vs. it’s), I love Paul Brians’ Common Errors in English Usage.
  • When in doubt, look it up.

Writing is a skill that can be taught, refined, and improved. And the written word is still a powerful tool. Learn to wield it well.

Loading mentions Retweet
Filed under  //   tips   writing  

Comments [0]

The average American consumes 34 GB of information in one day

Loading mentions Retweet
Filed under  //   databit  

Comments [0]

How to change how long your iPhone rings before calls get forwarded to voicemail

My iPhone always seems to jump to voicemail before I answer it. I need to increase the call forward delay. By increasing the delay before the call is transferred to voicemail, I have a better chance of grabbing it. As expected, the caller will hear an increased number of rings before being transferred. Works to decrease also. Google voicemail picks up at 25 seconds.

This requires a little friendly hacking. Call your iphone now from a different line to judge how long it takes to hit voicemail. 

1. dial the following: *#61# 
2. Press the Call button 
3. Write down your voicemail number. It's the number after "Forwards to" 

4. From the keypad dial the following: *61*1VOICEMAILNUMBER*11*30# inserting your voicemail number where VOICEMAILNUMBER is. It should be 11 numbers. 

(For example, if your voicemail number is 16787641111 then your command would be:*61*16787641111*11*30#

30 is the length of time in the command above. 20 is the default. 30 is the max. 

5. Press the Call button to send your command

6. You should see the following: 

Setting Activation Succeeded 
Voice Call Forwarding 
When Unanswered 

7. Congrats. You are set! Call your iphone again to see that it now takes longer to hit voicemail. 

If you screw up your phone, don't blame me. Do this at your own risk. If you want to be super safe, you can call AT&T and they will do this for you as well.

I used the method above to increase the time-before-forwarding-to-voicemail to 30 seconds. It worked!

Loading mentions Retweet
Filed under  //   att   iphone   voicemail  

Comments [0]