DDevelopment & Design

Agile UX – Confitura 2013

I już po tego rocznej confiturze… Odpowiadając na liczne zapytania po prezentacji “Agile UX – czyli jak połączyć zwinność z używalnością” zamieszczam poniżej zestaw materiałów do których nawiązywałem w trakcie prezentacji. W załączniku do tego wpisu znajdziecie też slajdy z prezentacji. Obawiam się, że nagranie z prezentacji może nie być udostępnione ze względu na problemy techniczne :( Kilka przydatnych linków:

User Interface (UX) Techniques – Janne Jul Jensen
Dave Nicolette – My personal agile journey
Advanced Common Sense
Agile UX – slajdy z prezentacji

P.S. Dzięki wielkie za feedback!

— Previous article

Touki na Confiturze

Next article —

Rozwój developera – TouK dla KarieraPlus

You May Also Like
NNews & Events

GeeCON 2010

  • byTouK
  • March 31, 2010
Zapraszamy na konferencję GeeCON 2010. TouK jest jednym ze sponsorów tej konferencji. Będzie można nas tam spotkać.
DDevelopment & Design

Distributed scans with HBase

HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?
DDevelopment & Design

New HTTP Logger Grails plugin

I've wrote a new Grails plugin - httplogger. It logs:

  • request information (url, headers, cookies, method, body),
  • grails dispatch information (controller, action, parameters),
  • response information (elapsed time and body).

It is mostly useful for logging your REST traffic. Full HTTP web pages can be huge to log and generally waste your space. I suggest to map all of your REST controllers with the same path in UrlMappings, e.g. /rest/ and configure this plugin with this path.

Here is some simple output just to give you a taste of it.

17:16:00,331 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,340 INFO  filters.LogRawRequestInfoFilter  - 17:16:00,342 INFO  filters.LogGrailsUrlsInfoFilter  - 17:16:00,731 INFO  filters.LogOutputResponseFilter  - >> #1 returned 200, took 405 ms.
17:16:00,745 INFO  filters.LogOutputResponseFilter  - >> #1 responded with '{count:0}'
17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,799 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,800 INFO  filters.LogRawRequestInfoFilter  - 17:18:55,801 INFO  filters.LogOutputResponseFilter  - >> #2 returned 404, took 3 ms.
17:18:55,802 INFO  filters.LogOutputResponseFilter  - >> #2 responded with ''

Official plugin information can be found on Grails plugins website here: http://grails.org/plugins/httplogger or you can browse code on github: TouK/grails-httplogger.