Om å skrive, analytisk

Om analyse. For meg så begynner grundig tenking og analyse med visualisering. Det kan skje visuelt med å tegne på en tavle eller ved å skrive ord, få opp en fasong på det vi skal se på, og deretter detaljeres flere og flere elementer.  Da kommer problemstillingene på rekke og rad.  Det er lett å vikle seg for langt inn, så en bør ofte gå ut igjen til helhetsbildet, etter å ha notert ned den grenen en fulgte ut litt.
            Så nå tenker jeg og skrivingen følger på.  Så redigerer jeg slik at det som står igjen er forståelig for meg selv.  Redigeringen er halve arbeidet.  Noen ganger mer.  Passer på å gruppere tekst før det blir for slitsomt å lese gjennom. Skiller tekst hvor det er logisk å ha et skille, slik at avsnittene blir logisk sammenhørende.

Det hjelper helt klart å ha gått veien før (gjort prosessen før).  Men det føles som noe nytt, hver gang man går veien. Det er helt enkle saker; forsøker å skrive det man tenker.  Så ser en at feil ord er brukt, eller at det kan misforstår.  Skrive-lese, skrive-lese.  Korriger hver gang det er nødvendig.  Vær opptatt av at resultatet skal være lett å forstå og at det skal være korrekt i forhold til forståelsesmodellen.
            Jeg jobber med datamodeller og har nok et i overkant datamodell-sentrisk syn på hva som bør stå hvor.  Dette faget (databasemodellering) går på hva som kan være entiteter og relasjonene mellom dem.  De er et supert verktøy for å dele opp konsepter og situasjoner og se på språket i mindre byggesteiner.

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 lecture others and more to
Les mer

Stupidly simple API code

I have written code intended for reuse by others in their applications. They have had access to me and could also extend the code themselves. I discovered today that someone have written new code of (low-level) functionality that it is already offered by the old code. Why? I can imagine, is that they didnt understand the old code properly. Maybe it was too complex. Maybe they didnt think it would offer that. Maybe they were in a too big hurry to ask me. Maybe they asked others who didn't know it as well either. Maybe the new code was so small they didnt bother to reuse old code. Is this possible to avoid this in the future? Maybe with complete tiny documentation of all our modules we could have avoided one of the reasons. I think the old code was too complex for them to understand. Thinking about this makes me leads me to believe the API of the old code is not really good. Its search API is not easy. There is a method for searching, but it is delegating search parts t
Les mer

Application sculpture

A good way to gain experience with anything, is to get your hands dirty.  In my case that would be to start implementing a system to gain experience with Java Spring programming framework. While I code the first draft of this system, I get some insights which I better jot down here before I loose my train of thought.  I have been thinking about rapid application development ideas for over a year, and think "how can a development such as this be made significantly faster and easier while keeping the expression power of contemporary programming platforms?", and "how would a development environment of the distant future look like?". The short version; To use a future programming environment today; search out and use a modelling tool like Poseidon for UML . The longer version; Implement a new development language. One that gives a totally new development environment, a new platform and new everything. One that dramatically shortens the time from modelling to test
Les mer