I Learnt

I have been developing a Maui application as a side project and on the whole it has been a fun process. It is still very buggy and there are some pain points however it seems to work. One aspect I haven't liked is the size of the build artefacts - they are huge if you have multiple projects.

"Put everything you know out for free but in a random order".

In the School of Greatness podcast with Rory Vaden he proposes that you should do exactly the above to build your brand and your opportunities.

I have a Dell XPS13 laptop and it developed this really annoying habit of randomly freezing for a few seconds and then carrying on as if nothing had happened. It quite often happened in the middle of a work call which made it pretty much unusable.

In a recent article/tweet the author commented on how all the photos taken by their child looked awful. However they realized this was down to a different generational mindset.

I have had lots of jobs during my life and I think I can identify at least one thing I have learnt at each of them. I usually know it is time to move to a new role if I no longer enjoy it or I am no longer learning something new.

About fifteen years ago, Casey Treat spoke at our church about goal setting. He explained that a lot of people set a goal of reaching a certain weight and he said the problem with that occurs when you reach that weight.

One of my favourite podcasts is Hanselminutes by Scott Hanselman. I have been listening to it probably longer than any other podcast. He recently interviewed Roberta Arcoverde from Stack Overflow. She talked about how the architecture of the Stack Overflow site is very different from most other large sites in that it is a self hosted monolithic application.

It is a classic way people start a conversation. Some people meet, they exchange a few pleasantries and then they ask "and, so what do you do?" And each person then takes turns, hopefully if someone doesn't just keep talking, explaining what their job is.