GT Spotter is a user interface that unifies the search workflow in an IDE. This set of slides was used for a submission at the ESUG 2015 Innovation Awards.
I watched 1800+ TED talks. I watched all those published on ted.com. Why? Because I am a TED addict. And because each of these talks reminds me that storytelling is essential in everything we do.
Facts are important, but facts alone have no value. They have to be consumed to worthwhile. Stories make this happen by getting us involved. This applies to researching novel ways, it applies to creating products, it applies to leading people, it applies to educating kids, and it applies to marriage proposals. Essentially, it applies to anything worth doing.
Storytelling is what makes stories happen. But, storytelling is a skill, and like any skill, it can be learnt.
For example, an easy way to learn is to listen to good examples. Like TED talks. But, there are many ways to learn. And, there are even more ways to apply.
It only takes us to invest in it. Why?
Because storytelling is essential.
Moose: how to solve real problems without reading codeTudor Girba
I use this set of slides for a talk I gave at ESUG 2014.
Abstract:
Moose is a platform for software and data analysis (http://moosetechnology.org). It runs on Pharo and it can help you figure out problems around software systems.
In this talk, I show several real-life examples of how custom tools built on top of Moose helped solve concrete problems. The examples vary both in scope and in the kind of problems. For example, we talk about how we fixed a caching problem in a Java system by analyzing logs, or how we fixed a Morphic problem by means of visualization and interaction. Even if these problems are so different, all of them were solvable with one uniform set of programmable tools.
That is the power of Moose, and it is now at the fingertips of any Pharo programmer.
We cannot continue to let systems loose in the wild without any concern for how we will deal with them at a later time. Two decades ago, Richard Gabriel coined the idea of software habitability. Indeed, given that engineers spend a significant part of their active life inside software systems, it is desirable for that system to be suitable for humans to live there.
We go further and introduce the concept of software environmentalism based on a simple principle: Engineers have the right to build upon assessable systems and have the responsibility of producing assessable systems.
The emergent nature of software systemsTudor Girba
This slideshow offers an argument for how the structure of a software system has an inherently emergent nature.
More information can be found at: http://humane-assessment.com
GT Spotter is a user interface that unifies the search workflow in an IDE. This set of slides was used for a submission at the ESUG 2015 Innovation Awards.
I watched 1800+ TED talks. I watched all those published on ted.com. Why? Because I am a TED addict. And because each of these talks reminds me that storytelling is essential in everything we do.
Facts are important, but facts alone have no value. They have to be consumed to worthwhile. Stories make this happen by getting us involved. This applies to researching novel ways, it applies to creating products, it applies to leading people, it applies to educating kids, and it applies to marriage proposals. Essentially, it applies to anything worth doing.
Storytelling is what makes stories happen. But, storytelling is a skill, and like any skill, it can be learnt.
For example, an easy way to learn is to listen to good examples. Like TED talks. But, there are many ways to learn. And, there are even more ways to apply.
It only takes us to invest in it. Why?
Because storytelling is essential.
Moose: how to solve real problems without reading codeTudor Girba
I use this set of slides for a talk I gave at ESUG 2014.
Abstract:
Moose is a platform for software and data analysis (http://moosetechnology.org). It runs on Pharo and it can help you figure out problems around software systems.
In this talk, I show several real-life examples of how custom tools built on top of Moose helped solve concrete problems. The examples vary both in scope and in the kind of problems. For example, we talk about how we fixed a caching problem in a Java system by analyzing logs, or how we fixed a Morphic problem by means of visualization and interaction. Even if these problems are so different, all of them were solvable with one uniform set of programmable tools.
That is the power of Moose, and it is now at the fingertips of any Pharo programmer.
We cannot continue to let systems loose in the wild without any concern for how we will deal with them at a later time. Two decades ago, Richard Gabriel coined the idea of software habitability. Indeed, given that engineers spend a significant part of their active life inside software systems, it is desirable for that system to be suitable for humans to live there.
We go further and introduce the concept of software environmentalism based on a simple principle: Engineers have the right to build upon assessable systems and have the responsibility of producing assessable systems.
The emergent nature of software systemsTudor Girba
This slideshow offers an argument for how the structure of a software system has an inherently emergent nature.
More information can be found at: http://humane-assessment.com
77. Class A method M
package 1
Class B method N
package 2
... ...
...
source code
78. w.
lat or ne ; #clas
s
GL MTabu mespaces de:
Outsi es.
b := mn: #na dTo
u es; b sen : #class #meth
od
b col mn: #class s. fro m ide:
colu : #method es; dT oOuts ods. ew.
n
colum : #namespa
c b sen : #meth ow ser n r'.
wOn from leLayoutBr Browse
b sho g: [ Tab ous
usin ee l | B := e: 'Glamor
b tr : [ :mode aces l
B tit #nav;
di splay allNamesp ; :
B row #details.
]
model : #isRoot pes; row: : #nav;
t o
selec : #childSc wOn
B sho g: [
en usin stom: b ].
c hildr #name ].
t:
forma lasses; [ B cu #details;
n: # c s; u sing: n:
showO #nav->#cla
ss;
showO #namespace B
b from: [
from: st s; : t ].
b li : #c lasse using xt ceTex
di splay #name ]. B te lay: #sour
t: disp etails;
forma ethods; #d ;
: #m es; using:
[
ho wOn: v->#method
wOn B s #na
b sho : #class f rom: [
from st ds; : ].
b li : # metho re ]. using xt c eText
display #signatu B te lay: #sour
t: disp
forma
79.
80. McCabe = 21
NOM =
102
OC
=
75
3,0
00
clas
ses
se lect
: #isG
o d
...
L
{ {
{ {
}
}
}
} { }