I learned a few things about rest apis. I put together some standards for the team. To use proper verbs, to treat REST as resources, which are managed. When that gets done on a consistent basis, things work out better.
I also started to make sure quality is maintained by the offshore team. I am trying to manage that and it’s not easy. Everyone wants to just do things, without seeing how it will affect quality.
Demanding quality. Establishing clear goals and work expectations. That’s something I need to do. That helps others.
I introduced RFCs at work, to happen before we are implementing a feature. I think that should help speed things up in terms of communication and also make sure that we design things better.
K8 supports configmaps, secrets, volume secrets and more. It’s something that I still have to master, but those options are quite good!
Spending time with your kids costs a little bit of my time, but it’s time well spent. I have to dedicate every day, up to 8:30 to work with my kids, to have them play with me and to turn off distractions. It’s something that’s hard, but it’s worth doing!
I learned one important thing about k8 and volumes. One of the volume types that is supported is git drives. I think that is probably something that needs to be backed up.
In terms of agile, user story maps and user impact mapping is something I need to keep researching.
In terms of k8, a service can be exposed as a nodeport, which exposes a single port, or as a load balancer, which will distribute the traffic between the multiple pods. That’s a clever way to doing things and the knowledge is falling into place.
I also learned in the category of gtd. It’s good to keep digging, keep challenging things. As a result, we made a potential breakthrough in our product. Though I will not get full credit, I had a major influence in shaping it and it feels good.
I have learned what a service is. It’s basically a LB for a pod. It gives a static IP that the services can use. It’s pretty cool!
I am also learning about writing good user stories. Best practice is to have them create value. Best practice is for them to be written from a stakeholder point of view. I need to hold that as a standard in how we do things, and I will try to learn about more practices and hold everyone accountable.
A leader is not a manager. Leading leads to X times performance, managing results in only 1 x. The difference is not even funny. The difference is amazing!
I consider myself a leader with integrity. It feels good when that is being validated by external people, by giving me advice. It also can be validated by just checking yourself. I responded to an email and responded in a frank, open way. No sugar coating. A few weeks later I can forward that email to someone that is important. And even though it’s a delicate subject, I am actually proud of my response. I am just doing my thing.
Is deploying locally via k8 is the best practice? It seems like it is. It’s something that has come a long way forward, and it’s now fairly easy to do, so I don’t really see why not. It simplifies and provides a unified approach to containers.
That said, I have a long way towards learning about it. It’s something I am investing time into, and it’s something that I will push hard so that we follow best practices.
I learned quite a few things. I delayed upgrading my linux laptop and I think I was due. New v18 of mandarin seem faster and more stable. I should be able to recapture at least a few weeks of lost time on the train.
I’ve also learned a few things about k8. Providing different configs for diff env type is something we might need to figure out.