4. nap

Minden rendben.

Úgy néz ki, hogy a kevesebb kávé jobb, úgyhogy holnaptól kevesebbet iszok. Be kell iktatnom zöld teát is valahova a napba.

A vádliaimban érzek egy nehézséget, húzást. Korábban ezt akkor éreztem, amikor fáradt voltam vagy a lábaim túl voltak terhelve, de volt még mellette egy általános fáradtság is. Mondjuk a mostani helyzet sincsen ettől messze.

Vannak időszakok, amikor az egész állkapcsom és ínyem sajog. Nem igazán értem, de aránylag rövid ideig tartanak ezek az időszakok.

Testsúly: 127,8 kg

Tetzsír: 32,5% (nem értem a mérleget… mindegy)

3. nap

Arról, hogy ez mi a kutyafüle itt tudsz olvasni.

Azt érzem, hogy a szellemi képességeim rendben vannak. Hoznak egy megszokott normáli szintet es tudom csinálni a munkámat. Jót tesz a 30+5 perces blokkok és a délbeni 20 perc szundi.

Érzelmileg mondjuk azt, hogy minden rendben van. Hülyeségek nem bukkannak fel. Pár óránként eszembe jut az étel. De távoli az egész.

Fizikailag már érzem, hogy néha-néha beharap a fáradtság és ez a kaja hiánya miatt van. Még 2-3 nap és be fogok lassulni arra a szintre, ami szokott lenni egy hosszabb böjtnél. Esetleg majd be kell iktatnom még egy 20 perces szundit valahova. Estére érzem, hogy elfáradok. Ma is 19:00 magasságában éreztem, hogy az arcom meleg, mintha arcpír lenne rajtam.

Kávé. Ma csak kettő dupla amerikánót ittam. Egy amerikánóval kevesebbet, mint szoktam. Nem tudom megmondani, hogy most jobb-e így vagy sem.

Aludtam kb. 8 órát és az a tegnapi fáradtság eltűnt reggelre és frissen ébredtem.

A nap nagy részében nyugalomban vagyok és van egy kényelmes áramlása a napnak. Nincs vagy nagyon alacsony stressz.

Testúly: 128,9 kg

Testzsír: 32,5 (ezt nem értem, de valszeg a mérleg ír ki hülyeségeket és pár anp alatt kiátlagolódik, hogy mit akar mondani)

2. nap

Arról, hogy ez mi a kutyafüle itt tudsz olvasni.

Tegnap valszeg belefutottam abba, hogy a böjt miatt nehezebben alszom el. Ez egy ismert jelenség számítottam rá. De ennek ellenére hajnali fél kettőig kukorékoltam és tudtam aludni épphogy 6 órát. Most érzem, hogy ez kevés volt. Mindezek ellenére jól érzem magam. Szellemileg friss vagyok. Érzelmileg semmi hullámzás. Van egy nagyon kicsi és kellemes izomlázam a tegnapi guggolásoktól. Összességében minden penge, csak aludnom kell most egy jót.

Testsúly: 129,8 kg

Testzsírszázalék: 31,5%

Ezekből a hétvégén maj csinálok valami grafikont.

Azzal a tervemmel, hogy kávéból kevesebbet kellene inni nem haladtam semmit sem. Majd holnap vagy leszarom…

A szokásos majd 3 km séta ma is megvolt, de azon kívül semmi sem. Fontos, hogy állva dolgozom. Estefelé szoktam csak leülni.

Ma sem ettem semmit sem. Habár ittam 3 kortynyi levest. Az erőleves (broth) azért jó, mert van benne jó sok minden, ami kell. Ezért is írtam, hogy ha van, akkor iszok belőle. Semmi szilárd, csak 1-2-3 korty a levesből.

1. nap

Súly: 131,8 kg

Arról, hogy mi ez az egész itt tudsz olvasni.

Sétáltam egy jót és csináltam pár guggolást. Azon gondolkodom, hogy napi szinten kellene testzsírszázalékot mérni. Ez segit kiegyensúlyozni a természetes súlyingadozást. Ha be tudom üzemelni a mérleget, akkor elkezdem ezt is.

Amit meg kell figyelnem és hoznom egy értelmes döntést, hogy mit fogok kezeni a kávéval. Mintha jobban ütne, hogy nem eszem. A jelenség az az, hogy amikor megiszom, akkor érzem, hogy tolja a fejemet. Lehet, hogy felére kellene csökkenteni elsőre és megvizsgálni, hogy mi történik. Mostanában dupla amerikánót iszok naponta kétszer. Lehet, hogy ezt a duplázást vissza kellene vinni szimplára.

Azt gondolom, hogy elég vizet iszom, mert nagyjából óránként bioszünet kell.

Nincsen érzelmi ingadozás, szellemi teljesítményem a normális szinten van. A munkában volt egy kicsi stressz, mert üldöz a tesztelői múltam. Valami egyedi fack-up összeállt és amire kibogoztam elment a nap és alig haladtam valamit.

Minden zsír.

Az egyetlen nehézség, hogy az egyik kedvencnek kikiáltott kávézoban kaptam nagyon finom házi kolbászt. Nos, ez az akarat próbája, hogy ne egyek belőle. Vagy ott fog a hűtőben csücsülni még pár hétig vagy szépen elfogyasztja a feleségem.

Ne csináld utánam.

What I’ve learned today?

I picked up a new habit recently, (By definition it can’t be called as habit, because I have been doing it only for 2 weeks, but… who cares!?) which is about collecting the new things I learned a given day. This daily, mainly the last things before sleep, exercise helps me to think through the day and filter the events of the day in multiple aspects.

I’m looking for data. It is the factual part of the events. I’m not really into factual data, but it is an aspect I need to deal with. Not to mentioned that being able to recall factual data forces my mind to really go into details.

I’m looking for references. If I watch a video about human body’s immune system, probably, I won’t memroise all the info I get from the material. Rather, I’ll remember the topic, some details, a few keywords and I create a reference in my mind to the video. Whenever I want to know something about immune system I can find this video and use it as a starting point.

I’m looking for connections or conclusions. Being able to recall a logical order of thoughts helps me to confirm whether the given process was good or not. It also creates mental notes to do things better.

Blazor – so far so good!

During my career I met different technology stacks and I poke them either as tester (either manual or test automation engineer) or just delivered software (basically didn’t give a damn what technology it is) as manager with the teams I worked with. The list includes php, java .Net and the mixed world of Big Data where everything is there in various quality. During the years I realised that .Net is the stack which gives me the most comparative advantage in my project and happiness in development.

The client side was always a pain point. HTML and CSS… meh… Javascript, what a huge pile of shit! As a consequence, I always avoided building the UI part of my app or when I did I gave up after a while because I just hate the fact I need to touch javascript/Typescript.

Angular 1.x eased the pain a little bit. Angular 2.x made Typescript default and we were close to what strongly typed languages can give you. But, still, webpack, linters, treeshake, npm hell! and other black magic… not to mention that the landscape changes in every 9-12 months or faster. It is an innovation hot spot and it is natural. But, still a clusterfuck.

Microsoft introduced Blazor in 2018. The promise is that you can use C# at both client and server side. Since .NetCore 3.0 is out I have been working with Blazor Server hosting model. The experience is great! C# is everywhere. I can debug easily my app using Rider (it still lacks proper support for Rider) and no struggle with contracts between JS app and server side. You just can share your domain objects and happiness.

Blazor still lacks features are default in Angular, but guys at Microsoft working hard to make Blazor a very compelling option to anyone.

 

My journey at IBM – Part II.: Learning opportunities

There is a site in IBMs intranet, called YourLearning and it is about what its name suggests.

There are very few things you, whoever you are, have to know about me. One of these is that I’m a knowledge junkie. I need to learn something new every day, and I need to expand the boundaries of my knowledge on daily basis. If it doesn’t happen, then I’m getting frustrated which is not good.

Again, I had preconceptions about IBM. I worked for a few multinational companies so far, all of them told me that they support learning, but there was a catch. There are no enough licenses, a subscription only for the crappiest learning site, or begging for a book costs 20 USD endless time so eventually you bought it for yourself. So, I started to browse IBM’s Your Learning site having the experience above in my head. And, suprise, I was wrong, again. Very wrong.

Just browsing the content I found thousands of available materials in multiple topics including every role available in a huge organization like IBM. Ok, sounds valid. After that I found a book and click… I was redirected to Safari Books. My heart almost jumped out from my chest! High quality technical books for whatever the hell you want to do in technical field! Because, I work for IBM I have access to this, and it is free.

Later as I got more familiar with the portal I found the learning sources section. Harward Business Publishing. It is the same in business/management field as Safari Books in technical field. Moreover, it is primary source for business literature. All the new stuff published here. In their digital library all the HBR articles are available.

Beside the two above, and the other I haven’t discovered yet, the portal helps you to track your progress in learning. Whatever you learned will be part of your profile and history, and you’ll get badges.

All in all, in my onboarding process I watch a video where Ginny Rometty talked about a journey in IBM where learning is essential. That time I had only the preconception I described above, now just scratching the surface of Your Learning portal I start to understand that IBM takes seriously learning. It points back to my expereince during interview process. With these resources I lot can be achieved…

And there are more I haven’t discovered yet.

My journey at IBM – Part I.: The People

I started my career at IBM Budapest Lab in mid February, 2020, as engineering manager. The reason I choose them is the people I met during interviews. I had my concerns regarding IBM, big company (~300 000+ employees), possibly big intertia (nothing happens or just slowly), rigidity and possibly uptight managers. It turned out that I was wrong. Very wrong.

The fact is that one of my friend and former colleague works at IBM Budapest Lab and he told me that the vibe is similar to what we had and loved in our previous job. “IBM, oh, yeah, sure…”

A few weeks later I had face check interview with 3 managers, now one of them is my line manager and the other two are my peers. I was surprised because all of them were nice, correct and professional, and the meeting ended up without any red flag from my side. No ego flare, no sign of power games, but clear interest who I am. All the topics were about how I deal with people, and no question whether I can write code this and that language. So far so good.

A few weeks later I met two other managers from the US and Canada. The result from my side was the same. No red flags, no points where I have to compromise my basics values. Moreover, it turned out that these managers are people focused and clearly understand that people are the key of success. This was the moment when I felt that I want to be member of this team, and work in an environment where people are more important than technology.

There is another picture built up in my thoughts while I was doing the interviews with IBM folks. Even though they are mainly people with strong technical background, it is clear they have a lot of knowledge and experience how to manage people. This complex knowledge was displayed by that they were able to translate my answer to their own language, and they double checked the meaning by asking questions. It is sign of paying attention to what I said (this is one of the hardest part of a manager job) and matching to their set of knowledge. One is not capable of this just having superficial knowledge. On the other hand, if the senior manager represents this quality the organisation will follow. This was convincing.

During my first day I met with both of the teams I’m going to work with. My first impression told me that there are no rockstar developers, no drama queens and no signs of ego issues, just rather humble team players. Later turned out that they have good sense of humor too. Wow! Kudos for the local managers!

 

Back to Github

When I started Digital Library project I gave a chance to the project management services provided by Github and they failed. Mainly because I didn’t know them and didn’t have enough patience to pick up some new knowledge, I wanted to move forward. In the following a few weeks the project got up to speed, so my goal was accomplished, and in my thoughts there was place to integrate something new. During this a few weeks I started to follow Microsoft’s open source projects, especially aspnetcore, dotnet/runtime and entityframeworkcore. As I read their tickets and pull requests I slowly understood how they integrate Github and Azure DevOps Builds. The result is that I put together a test project and tried Github – Azure DevOps integration in the most common scenarios I’m going to use. The result is that, finally, I started to use Github as I originally wanted.

One of the reasons I wanted to run my project fully on Github is self PR. Even though I don’t consider essential being on Github in my career, I’m an engineering manager and not a developer, but still being on Github and being able to display some professionalism might result something positive in the future. The other aspect is that, making your professionals transparent is a responsibility I have to deal with.

The lessons… First, you just have to understand when you are ready to absorb new knowledge, which may result some struggle and not the progress you seek. There is no such thing you are always able to integrate something new in your structured knowledge. This ability can be crippled temporarily by other priorities. In my case the need to be able to move forward was more important.

The other lesson is that you have to be able to define what is important for you. The way I wanted to manage my project was based on an earlier experience (14 developers, 4-6 feature developed in paralell, feature branches and multiple supported versions). My problem space is way simpler, and I was needed some time, and possibly clear head too, to understand it. Again, the need to be able to move forward clouded my judgment.

Anatomy of implemting a REST Api endpoint – Part Three

This writing is about how Azure DevOps can support software delivery.

So far there is a feature ticket about Dimension Structures CRUD functionality, and listing and adding new functionalities already implemented. Let’s see how Azure DevOps implement transparency in software delivery.

Dimension Structure CRUD ticket can display that to how many chunks (story tickets) this job was splitted and the status of these tickets. This way possible to track the progress of implementation without being distracted by lower level, development related information. Beside these you can use deadlines, risks and effort fields to track your progress, but, since I’m the only one working on this project I don’t use these.

Screenshot 2020-01-15 at 17.19.20

A story, attached to a feature as child, can show all the delivery related details you need to know to be able to see what happened. In my case the folowing data is displayed in a story ticket:

  • On which branch the implementation happened.
  • Build related information. There are two types of builds, one is just build, the other one is “Integrated in”.  You can attach multiple from both. I use the first type to mark the build where the full implementation successfully built on the server. Test results are displayed on the build page. In case of bigger projects it might be overkill. For me works fine. I use the “Integrated In” links to mark the build where the particular implementation went in to master branch. Master is the release branch.
  • Tasks for tracking different development related activities, and where you can track your time and remaining time. At this level also possible to mark a build where this job was completed/integrated. It is useful in case of bigger team where multiple developers work on a story. In my case, it would be overkill, however, builds automatically attached to the task.
  • Pull Request, which contains all the info needed to be able to review and merge the code change into master or other branches.
  • Test related stuff, I can’t use this part of Azure DevOps because I don’t use VS so I don’t know yet how to connect test cases in a dll to test cases in Azure DevOps. However, it is a really powerful feature and increases transparency.

Overall, when I put the delivery manager hut on my head and I want to know what is the status of the team deliveries then a well managed board can help a lot, especially when the tool, in this case Azure DevOps, does the majority of the work for you.

The master branch looks like this. Clean and lean…

Screenshot 2020-01-15 at 18.06.03

Feel free to dig the tickets in my Digital Library project.