Priorities of a computer programmer

How it is:
  1. Sketch
  2. Write code
  3. Test
  4. Deliver
How the agile people wants it to be:
  1. A working programming environment
  2. Make a rough design (not entirely true, but I will leave it as this)
  3. Write tests for next feature
  4. Write mock objects for sub systems
  5. Write code that complete the tests (get that green bar)
  6. Continue until next meeting by repeating from step 3 (next feature test)
  7. Get next feature set to implement by demoing the current product with customer and the payee
  8. Continue until payee says stop.

Kommentarer

Legg inn en kommentar

Populære innlegg fra denne bloggen

5 generations of computer languages

We control computers by writing code that is executed by the central processing unit (CPU). With an increasing degree, this code models the functions performed by the computer and its parts, and how they work together.  Such code has a syntax and semantics which together comprise a computer language.  Computer languages have during the last 50+ years undergone big changes.  They have become easier to use, more expressive and more structured than the first generations.   Note that the description of the computer language generations is subject to historical reviews and may change as one get further distance to the matter. However, for the past 10 and coming10 years or so, the current description should do. In the following presentation, some info are picked from Wikipedia [ H1 ] and some are mixed with my own info and viewpoints into a lethal cocktail which is probably neither correct nor complete. Read at your own risk!  My effort has been less to lec...
Les mer

DOJO kamptyper [forbedre egen kompetanse]

Noen ideer har poppet opp i det siste, trigget av dialog med kolleger; DOJO Code Battle / Showdown samme utfordring, implementer over begrenset tid, oppnå mest mulig funksjonalitet, fagfelle scoring, kan velge det språk/rammeverk en vil, kan gjentas flere ganger om en vil, til en får oppnådd og tilfredstilt sine egne krav til ytelse.  F.eks. kode en mikrotjeneste.  Tenk på en idrettsmann som øver på en ting til perfeksjon.  Dette gjør oss i stand til å gjøre løse ofte forekommende situasjoner raskt og effektivt, så vi kan bruke øvrig tid på andre saker, og gir oss selvtillit til at vi gjør en effektiv jobb. DOJO Theory Battle Hvor ulike forklaringer om samme konsept møtes for å bli enige om en felles forståelse, f.eks. bli enige om hva 'mikrotjenester' er.  Slik enighet om begreper er viktig for fremdrift og fellesskap; å dra i samme retning, få drahjelp, å hjelpe andre lenger i samme retning, å komme lenger enn en selv klarer, og å klare å snakke...
Les mer

Generations of text formats

In 1985, on a practice week in  some company downtown Bergen, I was lucky to get a course in Text editing software on Wang Computers.  Extensive use of function keys.  Very advanced functions, word-splitting, etc.  No font to select, very easy that way. In 1991, while visiting ABB in Heidelberg, Germany, as a student on a job acquired through IAESTE, I met my first text file format, the NROFF unix manual typesetting language. In 1992, I tried gopher hyperlink navigation. In 1993, the World Wide Web started for me, authoring web pages.  Setting up a web server. In 1997, while starting work on master thesis, I learned LaTeX.  \bold{text}.  Very powerful.  Even math equations.  Difficult with images.  Much more powerful than MS-Word.  Many templates available, for different end-results.  Each journal had their own format standards. Sometime 2000, a colleague looked into DocBook.  Also 2000s, I used Trac wiki and its syntax. S...
Les mer