The Coded One

programming, algorithms, discrete math, open-source

Nostalgia

with 6 comments

My Old Workstation

My Old Workstation

I miss…

looking at my small monitor, my old chair — aka ass poking device, our hacked air conditioner, going to Starbucks everyday, the “hot chicks”, the old elevator which keeps shutting down, sitting next to Tonio, talking about PHP oddities, triple escapes in regex, {} in sql queries, talking to Marvin, seeing him go nuts over SPAW2, seeing him go nuts over link scrubber

Written by Mark Basmayor

August 19, 2008 at 9:12 am

Posted in random thoughts

Tagged with ,

Banana stacks

leave a comment »

We should really start calling banana cues banana stacks because when you prepare them, the first one to get pierced is moved to the bottom of the stick, and when you eat them, you eat from the tip to the end of the stick. (Last In First Out)

Either start eating the bananas closest to your hand that’s holding the stick (First In First Out), or stop calling it a queue and call it a stack.

LOL!

Written by Mark Basmayor

July 17, 2008 at 5:15 am

Posted in random thoughts

Tagged with

Applying the Pareto Principle in Coding

leave a comment »

The Pareto principle (also known as the 80-20 rule, Haddad’s Theorem, the law of the vital few and the principle of factor sparsity) states that, for many events, 80% of the effects come from 20% of the causes. (http://en.wikipedia.org/wiki/Pareto_principle)

In programming this translates to, avoiding 20% of the bugs when writing code will reduce the effects of horrible bugs by 80%.

Less code = less bugs, no code = no bugs ? LOL

Written by Mark Basmayor

July 13, 2008 at 9:28 pm

Overview of Javascript Language

with 2 comments

The following is a lecture conducted by Yahoo! Javascript architect Douglas Crockford for the
Yahoo! UI Theater

Slides

Four-part Video

Written by Mark Basmayor

April 12, 2008 at 9:51 pm

Introduction to SVN

leave a comment »

What is SVN?

Subversion (SVN) is an open source code manager and version control system intended to replace CVS.  It is a system that manages files and directories, and the changes made to them over time.

Why use SVN?

SVN is great because

  • it remembers all the changes written to it: create, edit, update files/directories
  • it saves previous states, not just the current, so we can restore from a given date/version/etc
  • prevents concurrence issues like overwriting someone else’s work

Read the rest of this entry »

Written by Mark Basmayor

April 11, 2008 at 5:06 am

How to Use libcurl

with one comment

PHP supports libcurl, a library created by Daniel Stenberg, that allows you to connect and communicate to many different types of servers with many different types of protocols. libcurl currently supports the http, https, ftp, gopher, telnet, dict, file, and ldap protocols. libcurl also supports HTTPS certificates, HTTP POST, HTTP PUT, FTP uploading (this can also be done with PHP’s ftp extension), HTTP form based upload, proxies, cookies, and user+password authentication.  http://www.php.net

Read the rest of this entry »

Written by Mark Basmayor

April 10, 2008 at 2:08 am

Posted in PHP

Tagged with , ,

Handy Shell Commands

with 2 comments

shell

The Linux shell or sometimes called the command line or terminal is a text-based interface to the kernel. With the rise of GUI tools, some would think that there is no longer a need for this. But still, I am yet to find a GUI tool that can even compare with the simplicity, efficiency and power of the shell. For those who are new, here’s a list of commands that you might find helpful. Enjoy!

Read the rest of this entry »

Written by Mark Basmayor

April 6, 2008 at 9:15 pm

Posted in Linux, Ubuntu

Tagged with , , , ,

Best Coding Practices List

leave a comment »

These are some of the things that I learned from the talks made by our lead programmer Travis Low.

  1. If you find it too cumbersome to use very long variables, it’s ok to use shorthands or abbreviations but remember to refactor them later.
  2. Don’t use variables for multiple purposes.
  3. Avoid ifs.
  4. Use existing code .
  5. Publish code up into API/superclass.  Generalize to allow future changes.  E.g. wrappers, etc.
  6. Less code, less bugs.
  7. Think ahead.  Provide blank method definitions for very common methods or procedures.  E.g. checkForm()  Similarly, if you expect to use a parameter in the future, include it beforehand.
  8. If you’re as smart as you can be, how can you debug it?  Don’t try to put very fancy/technical codes because if something goes wrong in that code, you won’t be able to debug it.
  9. Be forgiving in your code, do not try to fix some data which will cause the system to break… instead try to correct the problem as you go or when instantiating
  10. Make someone want to use your code
  11. Don’t use double negatives when naming booleans.

Written by Mark Basmayor

April 3, 2008 at 2:50 am