-
Oof, took me an extra hour to get into work due to train issues. At least I got a walk out of it. I feel for these poor souls, stuck on the train until the problem gets fixed.
-
Amazing how time just grinds almost to a halt when you’re stuck on a train because of signal failure.
-
I met someone I used to work with at the supermarket today. I’m terrible with names, and it’s been more than a decade since I’ve seen her, so I couldn’t remember her name at the time. I recalled something from my memory just now and a LinkedIn search confirmed I got it right. Little victories today.
-
Oh great, now I need to upgrade my Gradle plugin just because I want to debug my app instead of just run it. How do people make forward progress in Flutter apps if they spend all their time upgrading things in their toolchain or replacing working code because they need to use a different package?
-
I’m looking at getting deep links working in a Flutter app. I haven’t got anything working at the moment. In theory I do have the server-side stuff in place, and I’m now looking at how I can get the Flutter app to handle the deep link.
There’s a recipes for doing this on Flutter’s website that I’m following now. It suggests downloading a separate package, go_router, to do the app routing. It’s published by the Dart team so I have some faith that it’s of decent quality, but why is this feature not in the core Dart library? I’ve already got navigation working using the Material router now. It already uses a path-based approach for navigation. Couldn’t this just be extended to support deep links as well? Was I wrong to use this router?
I think this is one thing that bothers me about Flutter development. The core libraries are pretty well design and do what they say that do, but only up to a point. They’re never extended to support additional use cases that would be, well… maybe not common, but certainly not unheard of, in a mobile app. Instead, we’re left to rip out what currently works and retrofit a package that doesn’t come in the standard library.
Don’t make me pull out working code. That’s never a good feeling. Just let me build on what’s already there.
-
Going through photos of my European trip, putting descriptions on them. Also updating my journal at the same time. I wish Day One supported photo captions. I have to settle for italic text below the photo if I want to add one. It’s left justified and just doesn’t look right.
-
🔗 XML is the future - Bite code!
I wanted to write something about fads in the software development industry when the post about Amazon Prime Video moving away from micro-services back to monoliths was making the rounds. A lot of the motivation towards micro-services can be traced back to Amazon’s preaching about them being the best way to architect scalable software. Having a team from Amazon saying “micro-services didn’t work; we went back to a monolith and it was more scalable and cheaper to run” is, frankly, a bit like the Pope renouncing his Catholic faith.
I didn’t say anything at the time as doing so seemed like jumping on the fad wagon along with everyone else, but I have to agree with this article that this following along with the crowd is quite pervasive in the circuits I travel in. I did witness the tail end of the XML fad when I first started working. My first job had all the good stuff: XML for data and configuration, XSLT to render HTML and to ingest HL71, XForms for customisable forms. We may have used XSD somewhere as well. Good thing we stopped short of SOAP.
The whole feeling that XML was the answer to any problem was quite pervasive, and with only a few evangelists, it was enough to drive the team in a particular direction. And I wish I could say that I was above it all, but that would be a lie. I drank the cool-aid like many others about the virtues of XML.
But here lies the seductive thing about these technology fads: they’re not without their merits. There were cases where XML was the answer, just like there are cases where micro-services are. The trap is assuming that just because it worked before, it would work again, 100% of the time in fact, even if the problem is different. After all, Amazon or whatever is using it, and they’re successful. And you do want to see this project succeed, right? Especially when we’re pouring all this money into it and your job is on the line, hmm?
Thus, teams are using micro-services, Kubernetes, 50 different middleware and sidecar containers, and pages and pages of configuration to build a service where the total amount of data can be loaded into an SQLite3 database2. And so it goes.
So we’ll see what would come of it all. I hope there is a move away from micro-services back to simpler forms of software designs; one where the architecture can fit entirely in one’s head. Of course, just as this article says, they’ll probably be an overcorrection, and a whole set of new problems arise when micro-services are ditched in favour of monoliths. I only hope that, should teams decide to do this, they do so with both eyes open and avoid the pitfalls these fads can lay for them.
-
Feature request for Micro.blog: have a way to recall a post entered into the Share Sheet when a user dismisses it. I wrote quite a lengthy post in one, and I lost it all when I accidently dismissed the Share Sheet. Doing that doesn’t feel great. 🙁
-
Best number plate seen on an electric car to date: CHGME. 🔋
-
I’m liking the new source browser in GitHub. Saves a decent amount of time for things like libraries where I just want to read the source. No more need for checking it out to a temp directory and opening it in an IDE just to get the code indexed.
-
Had the opportunity to see our new office today. It’s fabulous. Converted factory with exposed brick work gives it a startup feel. Lots of natural light as well. But the best thing is the commute: the small tram ride from Southern Cross is miles better than the bus. Looking forward to moving there.
-
The local Woolworths has rolled out what I believe to be E Ink price tags. I was hoping to start seeing E Ink used for things like this. The technology is perfect for this use case.
-
It’s a little frustrating seeing code examples that don’t explain what the example is trying to demonstrate. I found an example for an oauth2 Go library but there’s nothing about what it’s an example of. Is it of an authentication server? A resource server? What’s it demonstrating?
-
And just like that, my ChatGTP luck has run out. Asked it to generate some example code this morning, and what it produced couldn’t compile and misses a few key steps in the logic. I guess it won’t be doing my job anytime soon (I still find it really useful though).
-
A lawsuit, the last refuge of a scoundrel.
(With apologies to the Simpsons).
P.S. Like the new design of Birchtree.
-
🔗 Reddit mods fear spam overload as BotDefense leaves “antagonistic” Reddit
I wonder if anyone at Reddit’s C suite has ever been a moderator. That this API fisaco is affecting the tools that mods use to keep the community spam free and happy should give them pause. That they don’t care is an indication as to how detatched they are from those “on the ground”.
-
One last trip-related photo: the pseudo souvenir mug I bought. It’s a “pseudo souvenir” in that I didn’t get it overseas1. I saw mugs like this while I was in Venice, found myself wanting one after I left, so I got one from Red Bubble. It arrived at my house this Monday… but let’s pretend I bought it home myself. 🤫
-
Well, I did buy it while I was overseas, and it probably originated from overseas, but I didn’t bring it home with me. ↩︎
-
-
Code First, Tests After
Still doing the code first, tests after at work and I’m really starting to see the benefits from it. Test driven development is fine, but most of our recent issues — excess logging or errors that are false positives — have nothing to do with buggy business logic. It’s true that you can catch these in unit tests (although I find them to be the worst possible tests to write) but I think you gain a lot more just from launching the application and seeing it run. Continue reading →
-
A Lisp-based Evans Wrapper
I wanted an excuse to try out this Lisp-like embedded language Go library that was featured in Golang Weekly. Found one today when I was using Evans to test a gRPC endpoint and I wanted a way to automate it. Hacked up something in 30 minutes which takes a method name and a Lisp structure, converts it to JSON and uses Evans to send it as a gRPC message. As the afternoon progressed, I added some facilities to send HTTP GET and POST methods with JSON request bodies, plus some facilities to set some global options. Continue reading →
-
🔗 Poor man’s team bonding: recurring Slack threads
Could be a nice idea for blogs as well. Maybe for someone who’s trying to post at least once a day, but occasionally can’t think of something to write about. Not that I know anyone like that.
-
I can’t say enough good things about using Dokku for deploying and running web-apps on a Linux VPS. Compared to the competition, it’s so refreshing to use. Makes deployments the easiest part of the exercise, as it should be.
-
Interesting piece from the Verge about the rise and fall of Google Reader, which was killed 10 years ago. I wasn’t a big Google Reader user, and I still believe that the death of Google Reader was ultimately good for the RSS format. But I know how much people loved using it and how devastated they where when Google decided to pull the plug.
One thing that caught my eye was the executive’s comment about working on Google Reader being a waste of the engineers’ careers. Taking the comment at face value1, it doesn’t seem like a waste at all. Sure there were “only” 30 million users of Google Reader, but it’s obvious that they were passionate users of the service. And it would’ve been an honour working on something that elicit such a strong emotional response from your users, let alone being the one that started it all with the original prototype. I can’t imaging getting that same buzz by one of the thousands working on Google Search or Google+.
-
I’m guessing the comment was slightly coloured by the fact that the person making it wasn’t too keen on Google Reader. ↩︎
-
