No Stack Developer
A no stack developer criticizes the stack without understanding the stack. In addition to complaining, no stack developers engage in full rewrites, but don't finish them before quitting or getting fired, leaving an organization with no stack.
Twitter got people out here sending secret messages using Base64 encoded strings and QR codes.
Back in my day, we didn't need CI/CD, we had FTP. Real developers made changes in production.
Nice to see Docker desktop using MacOS's Virtualization Framework by default. Hopefully this means Docker can now run Intel x86_64 linux containers on ARM based Macs thanks to Rosetta.
https://developer.apple.com/documentation/virtualization/running_intel_binaries_in_linux_vms_with_rosetta
Running Intel Binaries in Linux VMs with Rosetta | Apple Developer Documentation
Run x86_64 Linux binaries under ARM Linux on Apple silicon.
The cloud is just someone else's computer, power, cooling system, underwater sea cables, networking equipment, data center and the land it sits on, control plane with support for Terraform, insurance policies, roadmaps, and a whole lot of people to build, secure, monitor, and support all of the software that runs on top.
I really appreciate API docs with curl examples.
That Addrs() method is implementation specific and the only way to do this from a unit test would be shelling out to setup new interfaces and assign IP addresses to them. Nope.
https://github.com/kelseyhightower/run/blob/master/network.go#L115
run/network.go at master · kelseyhightower/run
Package run provides helper functions for building Cloud Run applications. - run/network.go at master · kelseyhightower/run
The thing that makes testing that particular set of code hard is because net.Interface is a type and not an interface which would make it much easier for me to pass in my own implementation. There is no way for me to implement the Addrs() method for testing.
#GolangToday I find myself wrestling with the fact that some pieces of code are better off with integration tests because they are OS specific and require running commands to set up things like network interfaces. I just can't bring myself to doing that using unit tests. Here is the code in question:
https://github.com/kelseyhightower/run/blob/master/network.gorun/network.go at master · kelseyhightower/run
Package run provides helper functions for building Cloud Run applications. - run/network.go at master · kelseyhightower/run
Simon Willison
