Csabi's blog

[Desktop Entry] 
Type=Application
Version=1.0 
Encoding=UTF-8 
Name=Bluetooth Send to LG Viewty 
Icon=bluetooth 
Exec=/usr/bin/obexftp -b 00:00:00:00:00:00 -p %f

require "erb"

watch('tests/.*Test\.sh') do |md|
  clear_console
  run "#{md[0]}"
end

watch('source/(.*)\.sh') do |md|   # runs test when source code changes
  clear_console
  testpath = "tests/" + md[1] + "Test.sh"
  run "#{testpath}"
end

def clear_console
  puts "\e[H\e[2J"  #clear console
end

def run cmd
  result = `#{cmd} 2>&1`
  if result.match(/FAILED\s+\(failures=/)
    notify_failed cmd, result
  elsif result.match(/ERROR/) or result.match(/command not found/)
    notify "#{cmd}", result, "pending.png", 6000
  elsif result.match(/\nOK\n/)
    notify "#{cmd}", "<font size=4 color=lightgreen><b><i>Tests Passed Successfuly</i></b></font>", "success.png", 1000
  else
    notify "#{cmd}", "Unknown error: 
" + result, "pending.png", 3000
  end
  puts result
end

def notify_failed cmd, result
    ft = result.match(/.*(test.*)\nASSERT:(.*?)\n/m)
    first_failing_test = defined?(ft[1]) ? ft[1] : "no match"
    first_failure_message = defined?(ft[2]) ? ft[2] : "Critical"
 
    notify "#{cmd}", "<b>" + first_failing_test + "</b> failed!\n" +
      "<font size=3 color=pink><b><i>" + ERB::Util.html_escape(first_failure_message) + "</i></b></font>", "failure.png", 6000
end

def notify title, msg, img, show_time
  images_dir='~/.autotest/images'
  system "notify-send '#{title}' '#{msg}' -i #{images_dir}/#{img} -t #{show_time}"
end

@refresh_interval = 10000
start_timer(@refresh_interval)

def timerEvent(event)
	# your code to be run every @refresh_interval miliseconds
end

1. test only conditionally shown parts of a view (this includes text shown dynamically from objects or variables)
2. do not test for HTML tags or CSS selectors (only in special circumstances)
3. always try to match a text that should be visible

• High-level modules should not depend on low-level modules. Both should depend on abstractions.
• Abstractions should not depend on details. Details should depend on abstractions.

After all, can't you do everything equally well by pointing and clicking?
The simple answer is "no". [...] A benefit of GUIs is WYSIWYG - what you see is what you get. The disadvantage is WYSIAYG - what you see is all you get.

You should always write your code with S.O.L.I.D. in mind. Probably no programmer can achieve perfection but that doesn't mean you should not try to. Be a purist and code that respects these principles:
Single Responsibility
Open / Close
Liskov Substitution
Interface Segregation
Dependency Inversion

Thanks to the inventor of S.O.L.I.D., Robert C. Martin, any code can become much better by respecting just five simple principles.

1. A unique perspective about some common design patterns like Repository and Factory
2. The "Specification" design pattern invented by Evens and Fowler can and should be applied in many applications
3. Objects are categorized in an interesting way: entities, value object and services. Understanding these will change the way you see the code.
4. "Aggregates", a design pattern to decouple modules or groups of logically dependent classes and encapsulate functionalities of several objects. Very interesting even if it is hard to implement in certain programming languages.

Astazi a fost o premiera. Considerand ca era ziua inceperii anului scolar m-am hotarat sa-mi las masina acasa si sa ma duc la service cu role.

Proasta decizie

Desi unele trotuare sunt acceptabile, drumul pana la servici este un chin si plin de surprize. De exemplu ma gandeam sa traversez calea Lipovei la un semafor cu buton pentru pietoni. Fiind pe role si cu echilibrul mai imperfect, mi s-a parut cea mai sigura solutie. Macar cand traversez sigur nu trece nici o masina (la intersectii stiti si voi cum e cu verde simultan pentru masini si pietoni). E... asa, cu ideea pornita ma apropiu de trecere cand observ ca stalpul pe care e butonul e la vreo 2 metri de trotuar. Cu alte cuvinte trebuie sa iesi efectiv de pe suprafata asfaltata, sa te calci pe pamant (sau noroi daca ploua) ca sa apesi butonul pentru a face semaforul verde. Desigur, cu role pe pamant si pietrisi e un efort semnificativ de echilibristica.

Reusit, cu chiu-si-cu-vai, plus vreo doau priuete, se facu verde si traversat cu succes.

Mai departe spre Mall, pe partea dreapta a caii Lipovei. Trotuarul relativ bine asfaltat dar copacii lasati sa creasca pe unde vor. In multe locuri distanta pana la crengi e pe la 1.5metri ... cam greu cu rolele in aceste parti.

Dupa aceea au mai urmat vreo cateva sute de metri cu trotuar dezastru (zona centrului vechi), cu trecei de pietoni unde nici o masina nu incetineste sa poti trece si cu drumul la vreo 2 benzinarii spart deci traversarea pe role aproape imposibil (si mergand pe jos ar fi fost dificil).

Concluzie: poluare sau nu, la lucru cu masina, in parc cu rolele. As vrea eu sa protejez natura, dar nici sa-mi pun viata in pericol pentru asta.

Angry Birds on a physics exam

Via BoingBoing