Web Components are the future… at least that’s what this news letter I read said. I like the promise of web components. They basically, seem to me, to be Angular 5 / React like functionality built into standard HTML. They give you the ability to create new tags for HTML that do super special things. I’ve been wanting a way to publish and share some basic .ics (ICalendar) files on my running / triathlon site.
If you’ve ever worked on a project where you’ve tried to share code between two (or more) projects, you probably understand the pain. Sadly, I’ve worked on a few. Admittedly, on the surface it seems like a tempting proposition. On paper, it sounds quite easy. For example, one system I worked on we had a single nuget library where we kept our domain objects. The logic went: “All you have to do when you want to make a change is update the domain object project, build, push the new library to the nuget server, then pull down the new library to the other projects, and then rebuild those.
I am a big fan of using CI / CD. As most software engineers are. That’s not a very controversial stance. For open source projects there are some really nice services out there. One such service is Travis CI. I really like their service for open source projects, but I have a few side projects that I don’t want to open source. My side projects are not for monetary gain so there is no revenue from them.
I’ve been playing with writing my own Typescript / WebGL 3d game engine from scratch and fumbling about with machine learning (which oddly have a lot in common). The hobby has led me to studying linear algebra, which has got me looking at lots of problems in a different light. I blame a lot of my recent thinking on the YouTube Channel 3 Brown 1 Blue. The author of that channel lays out maths in a very visual way - it is much to my liking.
When building or designing software, I love to draw diagrams. I find the old adage “a picture is worth one thousand words” to be spot on. I also find that the diagrams are the most useful when they are right next to the source code. Having to drudge though a wiki or search though a separate documents folder to find the diagram that refers to the code I am looking at seems like a waste of time.
We’ve been moving a somewhat large site from a proprietary platform onto Wordpress. As you probably know, when you move a site from one platform to another, a lot of the URLs will change. In our case, amongst other things, many URLs went from having an .aspx extension to having none. On top of that, some features or pages just don’t exist anymore. To combat the URL confusion, we proactively monitor and attempt to fix 404s before, during, and for a few months after a move.
The end of the year is one of my favorite times of year. It’s when I see how I did with the goals I set for the current year and start to plan out my next adventures for the new year. I also like to either delete old ideas, or finish up random, playing-around code I have sitting in the old Projects folder. This year I made a conscious effort to refrain from putting out bits of code, but there are two proof of concept apps that I found useful and kind of fun.
Recently, I was doing some research on encryption for a project. I’ve used encryption libraries in past projects, but I’ve never written any actual encryption algorithms myself. And as the Internet does from time to time, I got sucked into looking around at the various algorithms. I came across an interesting encryption algorithm that I had never heard of. Apparently, it can not be cracked: the one-time pad. This is the one that most movies reference when you see the spy guy with his little flip book of paper.
« Newer Older »