Hovden Data Laboratory

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...

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...

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...

Some years ago, I bought Enerjy's Java Code Analyzer because it's pinpointing any bad code I might write. The good news now, is that this analyzer is free to use. It is an addon to Eclipse. You can let Eclipse get and keep having it updated by giving this URL to your Eclipse | Help | Install new software section:  http://update.enerjy.com/eclipse