Blaast Hackday on January, 24th 2012

Bandung Blaast HackDay Team in Action

Blaast Hackday session part 1

Blaast Hackday session part 1

Blaast Hackday session part 2

Blaast Hackday session part 2

Blaast Hackday session part 3

Blaast Hackday session part 3

Blaast Hackday

Blaast Hackaday is a Hackathon event where a fellow developers invited to building a mobile application in Blaast and they have to finish it in 8 hours. It’s fun to joining them even though the app I worked on with my team (@tyohan, @bepitulaz, and @ibnutri) is not finish yet.

Disclaimer

  1. The photos showed on this blog post is not belong to me. I took the photos from the Blaast Indonesia Twitter timeline.

Sebagian besar orang hanya memperdulikan tampilan

Design Inspiration: Stylish Toilets and Bidets Design from Stile

Hallo,

apa kabar semuanya? Semoga dalam keadaan sehat selalu. Di pagi buta hari Sabtu ini saya menulis blog post ini dalam keadaan yang baru saja sembuh dari sakit flu, batuk dan efek terlalu capek dalam bekerja. Sakitnya tidak terlalu berat memang, tetapi cukup mengganggu aktivitas harian saya sehingga memerlukan kurang lebih 2 hari untuk istirahat total. Yeah, this morning I’m back!

Di pagi yang sunyi ini saya memulai kegiatan hari Sabut ini dengan kegiatan yang tidak terlalu berat, yaitu membaca artikel mengenai user experience design yang berjudul “A prototype is worth a thousand words“. Saya tidak akan membahas mengenai apa yang saya pelajari dari artikel tersebut, tetapi mengenai pemikiran dari kutipan yang saya baca dari artikel tersebut:

Design isn’t just how it looks, Design is how it works

Steve Jobs

Kutipan diatas terdengar begitu dalam bukan? Makna yang saya tangkap dari kutipan diatas adalah desain yang bagus bukan hanya soal bagaimana sesuatu ditampilkan terlihat relatif baik, tetapi juga bagaimana sesuatu ditampilkan dengan baik dan berfungsi dengan benar. Sayangnya “sebagian besar orang” yang pernah saya temui seringkali hanya memperdulikan tampilan bagus dari perangkat lunak yang dibuat, tanpa memikirkan bahwa fitur-fitur yang dibuat juga harus bekerja sebagus desain tampilan yang dibuat.

Rasanya menyedihkan jika menemui perangkat lunak yang memiliki antarmuka yang relatif sangat bagus tetapi fitur-fitur yang ditampilkan tidak berjalan dengan baik. Analoginya seperti Anda ingin terlihat elegan dengan menggunakan busana yang mahal atau mewah tetapi cara berjalan Anda masih belum terlihat lebih elegan dari busana yang dipakai.

Jadi, kesimpulan yang saya ambil adalah antarmuka yang bagus itu hanyalah sebagian kecil kriteria dari perangkat lunak yang bagus. Anda tidak mau kan ketika menggunakan perangkat lunak dengan tampilan yang bagus, lalu ketika Anda menekan tombol “Calculate it!” perangkat lunak tidak melakukan apa pun, dan itu adalah momen yang cukup menyebalkan.

Jadi, Anda masih bersikeras bahwa pengguna itu hanya memperdulikan tampilan saja atau punya pendapat yang lebih baik?


Code template for get HTML form in NetBeans

In the past day, I wrote a blog post about the code template for post HTML form in NetBeans. Today I create another code template for get HTML form in NetBeans. Basically, it’s similar like the previous code template, but right now the method attribute value is get. Below is the code template that I explained before:

<form name="${name}" id="${id}" method="get" action="${action}" >
${cursor}
</form>

If you want to copy it, access the gist page or clone it by using the public gist URL git://gist.github.com/1524416.git. If you didn’t know how to add the new code template, maybe you want to check my another blog post that explain how to add a new code template in NetBeans IDE.

Enjoy!


Code template for post HTML form in NetBeans

Code templates are prewritten snippets of code provided by NetBeans IDE. You can paste a snippet into your code by using code completion or the template’s abbreviation followed by the Tab key.

http://netbeans.org/kb/docs/php/code-templates.html

NetBeans provided the code templates to makes the developers life easier, it’s a snippets of code that you can use to increase your development productivity. Such a tedious task if I have start over and over again to write an HTML form from the beginning. So I came up with an idea to create the code template for this one, a code template for post HTML form. Below is the code template of post HTML form:

<form id="${id}" action="${action}" method="post" name="${name}">
${cursor}
</form>

If you want to copy it, access the gist page or clone it by using the public gist URL git://gist.github.com/1519634.git. If you didn’t know how to add the new code template, maybe you want to check my another blog post that explain how to add a new code template in NetBeans IDE.

Enjoy!


Learn computer programming using JavaScript through Eloquent JavaScript ebook

Hello again, it’s Saturday now! A wonderful day where you can spend your free time with positive activities like computer programming. If this Saturday nite you are not going anywhere and want to learn a computer programming using JavaScript then you should start it from an ebook entitled Eloquent JavaScript written by Marijn Haverbeke. It’s great book for an introduction to computer programming.

The book exists in two forms. It was originally written and published in digital form, which includes interactive examples and a mechanism for playing with all the example code. This version is released under an open license.

http://eloquentjavascript.net/

Interested? So give your self a chance to try it and go to the official website of Eloquent JavaScript!

Have a great Saturday everyone!


Create a Code Template for console.log() in NetBeans

Hello again, how is your Sunday? Great? I hope so.

Today I write a lot of code in JavaScript and have to debug several code so I used the console.log() to see what’s the value contained in a variable I wrote before. I have to write many console.log() on the source code. I’m start looking if there is a code template in NetBeans so I can write console.log() more faster.

I look up the JavaScript code template list from NetBeans 7.0.1 installed on my Linux box and end up with a result there is no such code template for console.log(). So I added the new one for the console.log() by following these steps:

  1. Open the Tools menu from the NetBeans menu bar.
  2. Choose the options.

    Choose the options

    Choose the options

  3. Open the Editor tab and choose the Code Templates tab.

    Open the Editor tab and choose the Code Templates tab

    Open the Editor tab and choose the Code Templates tab

  4. Press New button to add new code template.

    Press New button to add new code template

    Press New button to add new code template

  5. Type the abbreviation of code template in New Code Template dialog box.

    Type the abbreviation of code template in New Code Template dialog box

    Type the abbreviation of code template in New Code Template dialog box

  6. Press OK.
  7. Add the expanded text aka the code template.

    Type the abbreviation of code template in New Code Template dialog box

    Type the abbreviation of code template in New Code Template dialog box

  8. Add the description of code template.

    Add the description of code template.

    Add the description of code template.

  9. Press OK button and it’s done!

To use the code template I just type conlog then press Tab to expand the template. The code template features provided by NetBeans is the feature I frequently use in daily coding.

Enjoy!


Quotes: Node has it’s own internal HTTP server which is capable of saving the state of the program and resuming it quickly when a new request is made.

…unlike in scripting languages like PHP, where the script is run once and then exits, Node has it’s own internal HTTP server which is capable of saving the state of the program and resuming it quickly when a new request is made.

http://book.mixu.net/ch2.html


Quotes: If any of your handlers call a blocking method, the entire server is blocked

In Node, the entire server has one single thread, so now your code must play nice. If any of your handlers call a blocking method, the entire server is blocked. Your code has to be constructed so that it always returns immediately and is called again when a response from the database or filesystem is ready. The difference from before is that the handler logic is split. Understanding this difference is the key to understanding Node.

http://project70.com/nodejs/beginners-tutorial-node-js/


Follow

Get every new post delivered to your Inbox.

Join 739 other followers