iDeas

iDeas:execute:=Inspire

March 6, 2013
by raffyrabin
0 comments

The Pragmatic Programmer Quick Reference Guide

Share
The Pragmatic Programmer Quick Reference Guide 5/5(100%) 2 votes

Care About Your Craft
Why spend your life developing software unless you care about doing it well?

Think! About Your Work
Turn off the autopilot and take control. Constantly critique and appraise your work.

Provide Options, Don’t Make Lame Excuses
Instead of excuses, provide options. Don’t say it can’t be done; explain what can be done.

Don’t Live with Broken Windows

Fix bad designs, wrong decisions, and poor code when you see them.

Be a Catalyst for Change

You can’t force change on people. Instead, show them how the future might be and help them participate in creating it.

Remember the Big Picture

Don’t get so engrossed in the details that you forget to check what’s happening around you.

Make Quality a Requirements Issue

Involve your users in determining the project’s real quality requirements.

Invest Regularly in Your Knowledge Portfolio

Make learning a habit.

Critically Analyze What You Read and Hear
Don’t be swayed by vendors, media hype, or dogma. Analyze information in terms of you and your project.

It’s Both What You Say and the Way You Say It
There’s no point in having great ideas if you don’t communicate them effectively.

DRY–Don’t Repeat Yourself
Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

Make It Easy to Reuse
If it’s easy to reuse, people will. Create an environment that supports reuse.

Eliminate Effects Between Unrelated Things

Design components that are self-contained. independent, and have a single, well-defined purpose.

There Are No Final Decisions

No decision is cast in stone. Instead, consider each as being written in the sand at the beach, and plan for change.

Use Tracer Bullets to Find the Target

Tracer bullets let you home in on your target by trying things and seeing how close they land.

Prototype to Learn

Prototyping is a learning experience. Its value lies not in the code you produce, but in the lessons you learn.

Program Close to the Problem Domain

Design and code in your user’s language.

Estimate to Avoid Surprises

Estimate before you start. You’ll spot potential problems up front.
Iterate the Schedule with the Code

Use experience you gain as you implement to refine the project time scales.

Keep Knowledge in Plain Text

Plain text won’t become obsolete. It helps leverage your work and simplifies debugging and testing.

Use the Power of Command Shells

Use the shell when graphical user interfaces don’t cut it.
Use a Single Editor Well

The editor should be an extension of your hand; make sure your editor is configurable, extensible, and programmable.

Always Use Source Code Control

Source code control is a time machine for your work—you can go back.

Fix the Problem, Not the Blame

It doesn’t really matter whether the bug is your fault or someone else’s—it is still your problem, and it still needs to be fixed.
Don’t Panic When Debugging

Take a deep breath and THINK! about what could be causing the bug.
“select” Isn’t Broken.

It is rare to find a bug in the OS or the compiler, or even a third-party product or library. The bug is most likely in the application.
Don’t Assume It—Prove It
Prove your assumptions in the actual environment– with real data and boundary conditions.

Learn a Text Manipulation Language.

You spend a large part of each day working with text. Why not have the computer do some of it for you?

Write Code That Writes Code
Code generators increase your productivity and help avoid duplication.

You Can’t Write Perfect Software

Software can’t be perfect.

Protect your code and users from the inevitable errors.

Design with Contracts

Use contracts to document and verify that code does no more and no less than it claims to do.

Crash Early

A dead program normally does a lot less damage than a crippled one.
Use Assertions to Prevent the Impossible

Assertions validate your assumptions. Use them to protect your code from an uncertain world.

Use Exceptions for Exceptional Problems
Exceptions can suffer from all the readability and maintainability problems of classic spaghetti code. Reserve exceptions for exceptional things.

Finish What You Star

Where possible, the routine or object that allocates a resource should be responsible for deallocating it.

Minimize Coupling Between Modules

Avoid coupling by writing “shy” code and applying the Law of Demeter.
Configure, Don’t Integrate

Implement technology choices for an application as configuration options, not through integration or engineering.

Put Abstractions in Code, Details in Metadata

Program for the general case, and put the specifics outside the compiled code base.

Analyze Workflow to Improve Concurrency

Exploit concurrency in your user’s workflow.

Design Using Services

Design in terms of services—independent, concurrent objects behind well-defined, consistent interfaces.

Always Design for Concurrency

Allow for concurrency, and you’ll design cleaner interfaces with fewer assumptions.

Separate Views from Models

Gain flexibility at low cost by designing your application in terms of models and views.

Use Blackboards to Coordinate Workflow

Use blackboards to coordinate disparate facts and agents, while maintaining independence and isolation among participants.

Don’t Program by Coincidence

Rely only on reliable things. Beware of accidental complexity, and don’t confuse a happy coincidence with a purposeful plan.
Estimate the Order of Your Algorithms
Get a feel for how long things are likely to take before you write code.

Test Your EstimatesMathematical analysis of algorithms doesn’t tell you everything. Try timing your code in its target environment.

Refactor Early, Refactor Often

Just as you might weed and rearrange a garden, rewrite, rework, and re-architect code when it needs it. Fix the root of the problem.

Design to Test

Start thinking about testing before you write a line of code.

Test Your Software, or Your Users Will
Test ruthlessly. Don’t make your users find bugs for you.

Don’t Use Wizard Code You Don’t Understand

Wizards can generate reams of code. Make sure you understand all of it before you incorporate it into your project.

Don’t Gather Requirements–Dig for Them

Requirements rarely lie on the surface. They’re buried deep beneath layers of assumptions, misconceptions, and politics.
Workwith a User to Think Like a User
It’s the best way to gain insight into how the system will really be used.

Abstractions Live Longer than Details
Invest in the abstraction, not the implementation. Abstractions can survive the barrage of changes from different implementations and new technologies.

Use a Project Glossary

Create and maintain a single source of all the specific terms and vocabulary for a project.

Don’t Think Outside the Box–Find the Box

When faced with an impossible problem, identify the real constraints. Ask yourself: “Does it have to be done this way? Does it have to be done at all?”

Start When You’re Ready.

You’ve been building experience all your life. Don’t ignore niggling doubts.

Some Things Are Better Done than Described

Don’t fall into the specification spiral—at some point you need to start coding.

Don’t Be a Slave to Formal Methods.

Don’t blindly adopt any technique without putting it into the context of your development practices and capabilities.

Costly Tools Don’t Produce Better Designs

Beware of vendor hype, industry dogma, and the aura of the price tag. Judge tools on their merits.

Organize Teams Around Functionality

Don’t separate designers from coders, testers from data modelers. Build teams the way you build code.

Don’t Use Manual Procedures
A shell script or batch file will execute the same instructions, in the same order, time after time.

Test Early. Test Often. Test Automatically

Tests that run with every build are much more effective than test plans that sit on a shelf.

Coding Ain’t Done ‘Til All the Tests Run
‘Nuff said.

Use Saboteurs to Test Your Testing

Introduce bugs on purpose in a separate copy of the source to verify that testing will catch them.

Test State Coverage, Not Code Coverage
Identify and test significant program states. Just testing lines of code isn’t enough.

Find Bugs Once
Once a human tester finds a bug, it should be the last time a human tester finds that bug. Automatic tests should check for it from then on.

English is Just a Programming Language
Write documents as you would write code: honor the DRY principle, use metadata, MVC, automatic generation, and so on.
Build Documentation In, Don’t Bolt It On
Documentation created separately from code is less likely to be correct and up to date.

Gently Exceed Your Users’ Expectations
Come to understand your users’ expectations, then deliver just that little bit more.

Sign Your Work
Craftsmen of an earlier age were proud to sign their work. You should be, too.

Languages To Learn:
Tired of C, C++, and Java? Try CLOS, Dylan, Eiffel, Objective C, Prolog, Smalltalk, or TOM. Each of these languages has different capabilities and a different “flavor.” Try a small project at home using one or more of them.

The WISDOM Acrostic:
- What do you want them to learn?
- What is their interest in what you’ve got to say?
- How sophisticated are they?
- How much detail do they want?
- Whom do you want to own the information?
- How can you motivate them to listen to you?
- How to Maintain Orthogonality
- Design independent, well-defined components.
- Keep your code decoupled.
- Avoid global data.
- Refactor similar functions.
- Things to prototype

Architecture:
- New functionality in an existing system
- Structure or contents of external data
- Third-party tools or components
- Performance issues
- User interface design
- Architectural Questions

Are responsibilities well defined?
- Are the collaborations well defined?
- Is coupling minimized?
- Can you identify potential duplication?
- Are interface definitions and constraints acceptable?
- Can modules access needed data—when needed?
- Debugging Checklist

Is the problem being reported a direct result of the underlying bug, or merely a symptom?
Is the bug really in the compiler? Is it in the OS? Or is it in your code?
If you explained this problem in detail to a coworker, what would you say?
If the suspect code passes its unit tests, are the tests complete enough? What happens if you run the unit test with this data?
Do the conditions that caused this bug exist anywhere else in the system?

Law of Demeter for Functions
1. An object’s method should call only methods belonging to
Itself.
2. Any parameters passed in
3. Objects it creates
4. Component objects
5.How to Program Deliberately

- Stay aware of what you’re doing.
- Don’t code blindfolded.
- Proceed from a plan.
- Rely only on reliable things.
- Document your assumptions.
Test assumptions as well as code.
- Prioritize your effort.
- Don’t be a slave to history.
- When to Refactor

You discover a violation of the DRY principle.
You find things that could be more orthogonal.
Your knowledge improves.
The requirements evolve.
You need to improve performance.
Cutting the Gordian Knot

When solving impossible problems, ask yourself:
- Is there an easier way?
- Am I solving the right problem?
- Why is this a problem?
- What makes it hard?
- Do I have to do it this way?
- Does it have to be done at all?
- Aspects of Testing

- Unit testing
- Integration testing
- Validation and verification
- Resource exhaustion, errors, and recovery
- Performance testing
- Usability testing
- Testing the tests themselves

Checklists from The Pragmatic Programmer, by Andrew Hunt and David Thomas. Visit www.pragmaticprogrammer.com.

Share

December 11, 2011
by raffyrabin
0 comments

Ideas, Ideas, Ideas

Share

ideas1
ideas17
ideas3
Save the nature
ideas10
ideas18
ideas9
ideas2
ideas4
ideas5
ideas6
ideas13
NextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnail
Share

October 21, 2011
by raffyrabin
0 comments

NYC – Comic Con 2011

Share
NYC – Comic Con 2011 5/5(100%) 1 votes

NextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnailNextGen ScrollGallery thumbnail
Share

September 30, 2011
by raffyrabin
0 comments

On Building a Fascinating Product

Share

As part of any market strategy, build a fascinating product seems to be a critical factor for that products success rate. I’ve copied a few except below and hope you find it helpful to increase your products value.

“These results raise the obvious question: what does it take to be fascinating?…
1. Lust: the anticipation of pleasure, which we crave.
2. Mystique: unanswered questions, which intrigues us and makes us want to solve the puzzle.
3. Alarm: the threat of negative consequences, which demands immediate response.
4. Prestige: symbols of rank and respect, which earn us status and admiration.
5. Power: command over people and things, which draws our focus.
6. Vice: rebellion against rules, which tempts us toward “forbidden fruit.”
7. Trust: certainty and reliability, to which we give our loyalty.

The business implications of being able to employ these triggers can be significant. According to the research, a fascinating brand can charge more than an un-fascinating one, up to four times as much. People also will pay a premium for brands that activate desired triggers. In the presence of a
fascinating product, 80% of people report a strong emotional or physical response.”

Click here to view full article

Share

June 8, 2011
by raffyrabin
0 comments

Formula for Success

Share
Formula for Success 5/5(100%) 1 votes

/***********Secret Formula for Success ***********/
Don’t study. Stay dumb.*

*Proof:
Eq 1: Knowledge = Power (Sir Francis Bacon)

Eq 2: Power = Work output / Time (Physics)

Eq 3: Time = Gold (Business Majors)

Now…
1.] Substitute Eq. 3 to Eq. 2:
Power = Work output / Gold (eq. 4 )
2.] Substitute Eq. 4 to Eq. 1 and multiply both sides of the equation with (Gold/Knowledge) will give:
     Gold = (Work output/Knowledge)

SO…as Knowledge approaches zero, Gold approaches infinity!

Credits: Couz Darren!

Share

November 20, 2010
by raffyrabin
1 Comment

BabaGanush

Share

Create an iPhone Photography application that
creates a photos slide-show from the following sources:

  • Upload from your mobile Photo
    Library
  • A URL
  • Facebook -
    Using Facebook Connect API
  • Flicker – Using
    Flickr API

Slide-show
have the ability to optionally add music from your music library or
a music url

Social Sharing
Features

  • Email
  • Facebook Share
  • ***Tweet***
  • Other Social
    Media
Share

November 1, 2010
by raffyrabin
1 Comment

OpenContent

Share

OpenContent – Basic Functionality

GIT Source Control Repo

Basic Workflow Diagram, Click Below


What is it? OpenContent (OC) is an “Open News Platform” site where any contributors or users can submit “Original” news articles based on a category (mandatory): Local News, The World, Technology, Sports and Lifestyle.

Moderation of submitted articles is user-based, meaning other contributors and/or site users gets to approved, suggest revision, reject the submitted article before it gets published online on the site for the selected category.

A Contributor’s article, gets notified via email that the article have been approved and published online. User can opt-out from being notified from his Profile Settings.
What’s in a Published Article?
  • 1. Contributors avatar/photo
  • 2. Link to contributors profile
  • 3. Contributors list of published articles.
  • 4. Rating for this contributor from other contributors and/or users and the ability for other users to rate the article.
  • 5. The Article.
  • 6. Social sharing link (Facebook, Twitter, etc.)
  • 7. Report abuse link form base (jQuery)
  • 8. Contact email link form base (jQuery)
  • 9. Vote this! The “Vote this” link which will be on every articles is a way for the article to get pushed to the main Category section of the page.
  • 10. All submitted article must be original. Copyrights and article content is solely owned by that Article Contributor and the site is remains solely a broker for publishing those articles.
What’s in “The Article”
  • 1. Article Subject
  • 2. Main article text
  • 3. Photo or a Photo Gallery
  • 4. Video
Contributors Profile Page
  • 1. Personal Info – Avatar, Interest
  • 2. If logged in, show WYSIWYG Editor with a Save Later and Publish Now buttons
  • 3. If logged in, show pending articles for with 2 buttons, approve, revise (proof-read), reject from other contributors.
  • 4. All Published articles with comment moderation, removal
  • 5. All published articles can be edited
  • 6. Edited published articles is removed from the published queue and re-submitted to the origina approvers with the edited text highlighted for re-approval and once approved will go back on the main site with an additional information: Edited on: (date)
  • 7. All published articles can be removed only by 2 users: Submitter and Site Admin / Moderator
Share

November 1, 2010
by raffyrabin
1 Comment

vClassRoom

Share
vClassRoom 5/5(100%) 1 votes

Virtual Classroom

  • 1. Schedule any online class by category
  • 2. Any users can participate to a class
  • 3. Teachers and Students can both share their computer
    and grant control to anyone who’s signed up and attending the class
    for full interaction
  • 4. Ability to use camera,
    mic, phone, chat box
  • 5. Interface is purely
    web-based (you only need browser: IE, Mozilla Firefox, Safari,
    etc.) and NO additional software installation is
    required
Share

November 1, 2010
by raffyrabin
0 comments

Get it Fast

Share

Get it Fast There

  • 1. This is a web-based site that serves as a broker between buyers and sellers (much like the ebay).
  • 2. Turn around time for getting any item/s purchased from the site should at least be within 60 minutes. No need to wait for USPS, UPS, FedEx, DHL, etc for your item to get shipped.
  • 3. Seller delivers the item to you or to your receiver using several options:
    • 3.1 In-Person
    • 3.2 Drop-off to a valid location were you can easily pick-up the item, such as an office, lobby, etc (all you need is a proof of identification).
  • 4. Works mostly on Metro area, such as New York, Boston, LA, San Francisco, Chicago, etc.
  • 5. Gives out detailed feedback and ratings for credibility of sellers from buyers so you know your item is secured and safe and will get there on time.
Share

November 1, 2010
by raffyrabin
0 comments

Healthy and Free

Share
Healthy and Free 5/5(100%) 1 votes

Healthy and Free

  • 1. Personal Health Site – Single Page layout model (no
    page re-direct, use Ajax, JQuery, etc).
  • 2.
    Personalization: Template driven based on user preference.
  • 3. Users specific look_and_feel based on
    their roles:
    • 3.1 Medical Practitioner: Nurse,
      Nursing-Aid, Med-tech, Radiologist, etc.
    • 3.2
      Physician: Doctors (MDs)
    • 3.3
      Patients
    • 3.4 Multiple roles, combination of
      3.1, 3.2 and 3.3
  • 4.
    Healthcare Management Features (ALL in Realtime Transactions)

    • 4.1 Practice Management Software: Scheduling,
      Referrals/Second-Opinion, Insurance Benefits check, Billing and
      Claims (EDI)
    • 4.2 Calendar (with notification)
      features for appointments (confirmed/pending, etc.), Medication
      Refills, etc.
    • 4.3 Electronic Medical Record
      Management (EMR)
      • 4.3.1 Realtime Orders /
        Results: Laboratory, Radiology
      • 4.3.2
        ePrescription Orders with Delivery Confirmation: Online or Fax
        options
      • 4.3.3 Patient Health Record
        Management: Allergies, Medications, Lab/Rad Results, Health
        History
    • 4.4 Charting
      and Care Documentations
      • 4.4.1 Specific to area
        of care: Pediatrics, Internal Med, Neuro, Opta, Pulmo, Surgery,
        Gynecology, etc.
    • 4.5
      Security and Privacy
      • 4.5.1 User’s can grant
        access privilege and the ability for other users to control their
        own clinical records such as viewing, adding, editing, updating and
        deletion of the said records
      • 4.5.2 Critical
        health information are flagged automatically to be hidden from
        everyone except for the following:
        • a. Record
          Owner (a.k.a Patient)
        • b. PCP (if
          applicable).
        • c. Ordering Physician.
        • d. The patient will literally “own” this type of record
          and can set it to be hidden from everyone.
        • e.
          In emergency cases where a “locked” record is kept and the patient
          is in-incapacitated, any attending physician and/or medical
          practitioner can open the locked information ONLY if they provide
          the following credentials:
          • 1. Full name and
            Designation: Nurse, PCP, Attending Physician
          • 2. Medical License # (if Nurse, PCP, Attending Physician)
            or Any Government Issued Picture ID (Only applies to
            relatives)
          • 3. eSigned Emergency Release Form
            with specific emergency reason (can be a simple list of check
            boxes)
    • 5. Up-to the second update from
      your social network.
    • 6. Search filter for
      best-of-the-best Physician around
      • a. This will
        be based on user ratings, comments, education profile and
        recommendations from other users.
    • 7. Participate and help in various research
      study to find a cure to diseases such as HIV/AIDS, Cancer, and
      similar forms of illness.
      • a. Privately
        correlate similar medical information you have within the network
        and also have an option to share your own information to others
        (see privacy settings).
    • 8. Social eHealth:
      • 8.1 System
        self-evolves and gives out trivial information about your
        well-being, such as recommended diet that works for other
        users.
      • 8.2 Create groups to help facilitate
        and organize events in helping and reaching out to other users in
        the system with common interest.
    • 9. Purely web-based and accessible via the Internet. Can
      integrate seamlessly to 3rd party vendors (PMS, EMRs,
      Pharmacies).
    • 10. TOTALLY FREE – Marketing and
      business model to be announced soon.

Recommended reference site: Thomas Goetz: It’s time to redesign medical data

Share

iDeas is Digg proof thanks to caching by WP Super Cache