Skip to main content

2014

Hienoa uutta opittua

  • JavaScriptin perusteet, erityisesti AngularJS. Mukana kahdessa pienessä projektissa, joissa käytettiin AngularJS:ää.
  • Kimono API, jopa niin paljon että pidin esityksen työpaikallani!
  • OSGI, oppiminen jatkuu. Toimii hienosti Vaadinin ja Pushin (http) kanssa.
  • SCSS. SCSS:llä on ytimekkäämpi ja monipuolisempi syntaksi. Laaja projekti voidaan jakaa semanttisesti useampaan eri tiedostoon.
  • Clean code, 5 riviä per metodi. Vältä kommentteja! Metodin nimen pitää olla sellainen että kommentteja ei tarvita. 
  • Design patternien tärkeys, kun koodin määrä kasvaa. Tärkeää että kaikki koodaajat hyväksyvät valitut patternit ja käyttävät niitä yhdenmukaisesti. Myös uudet kehittäjät täytyy perehdyttää miten patternia käytetään.
  • Töiden tekeminen käyttöliittymäsuunnitelijan kanssa. Käyttöliittymäsuunnittelussakin pätee sääntö "älä keksi pyörää uudelleen". Käyttöliittymässä pitää olla tuttuja elementtejä. Tämä ei kuitenkaan tarkoita, että kaikki pitää uudelleen kierrättää. Kuten mikä tahansa muukin idea/keksintö: perustuu edelliseen mutta tuo kuitenkin jotakin uutta.
  • Millaista on olla suuressa projektissa, jossa on monta tiimiä. Asiat kuten koodin luettavuus ja mielipiteiden ilmaiseminen tulevat esiin tärkeimpinä.

Pohdittua

  • Kokoustaminen. On vaikeaa arvioida onko jokin kokous turha vai hyödyllinen. Mikä on kokouksen ja juttutuokion ero? Pitääkö kokouksella aina olla agenda ja pitääkö kokouksen johtaa aina päätökseen?
  • Pitääkö kaikkien työntekijöiden olla ajan tasalla projektin tapahtumista koko ajan?


Comments

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...

Bird is causing high CPU on my macOS

There is no lack of people complaining about MacOS Tahoe, mostly about rounded corners and inconsistent design decisions. I have not paid that much attentention to that, but there is one mac bug i have paid attention to. It hasn't been a visual or ux but rather few system processes pegging the CPU. trustd , alongside with ecosystemd and ecosystemanalyticsd all reported high CPU usage. I can't exactly recall when this started, it might have predated my Tahoe upgrade but anyway, the trio of processes all had high CPU usage. Sure, it may have been the virtual efficiency cores and whether it affeced battery life or slowed down other processes i don't know to be hon...

Ousterhout's law

Back in the day, everyone was using Winamp. It is a music player with the user interface of a mixing console. The bloody thing had an equalizer on the front page! As an amateur music producer, I know that EQ is a powerful tool but making changes that sound good is difficult, to say the least. Mixing engineers spend considerable effort with the artist to balance the frequency ranges to arrive at the desired musical outcome. I bet the 15-year-old me butchered a lot of songs with the thing. Now we are using Spotify, a player with basically a search bar and a play button. I ran into something called Ousterhout's Law on the  Operating Systems: Three Easy Pieces book . Here is a quote from the book TIP: AVOID VOO-DOO CONSTANTS (OUSTERHOUT’S LAW) Avoiding voo-doo constants is a good idea whenever possible. Unfortunately, as in the example above, it is often difficult. One could try to make the system learn a good value, but that too is not straightforward. The frequent result: a configura...