Correction: Canada is a country with a small number of large cities that determine the national government. There are whole regions of the country that have no representative voice within the governing parties.
After many years, I’ve come to the same conclusions and can heartily recommend these suggestions!
Another similar suggestion I’d add is make a settings module with a base collection of configuration (i.e. myproject/settings/common.py) that other deployment-specific dev.py & prod.py import from.
Basically, don’t forget that Django projects are always Python modules too, so go ahead and use those language features too.
Last week I signed up for an annual subscription to MDN. I didn’t realize it at the time, but paying subscribers get the option to enable offline mode (it currently downloads about 630 MiB of content). I generally have fast connections wherever I’m working, but the difference between “fast” and “instant” when loading new pages is really making the experience feel special for me. I would heartily suggest you support MDN and try it out!
I once purchased a FireWire multi-channel audio interface with the express intent of reverse engineering the protocol in order to add Linux support. I purchased a specialized PCI card that was intentionally non-standard (not OHCI 1394) but could snoop and capture traffic between a device and a host. I chipped away at deciphering a register map for awhile, but eventually better USB audio devices came along that had more driver support.
Still trying to do the same sort of thing though with some audio related USB and Ethernet/IP devices so I guess I never really gave up the idea in my heart!
A Go vendoring pattern that I've found very useful is to use two repositories, the first for the main "project" repository, then a second "vendoring" repository that imports the first as a module, and also vendors everything.
This may require a few extra tricks to plumb through, for example, to make all cmd's be externally importable (i.e. in the project repository, transform "cmd/foo/%.go" from being an unimportable "package main" into an importable "cmd/foo/cmdfoo/%.go", then have a parallel "cmd/foo/main.go" in the vendoring repository that is just "func main() { cmdfoo.Main() }", same as you have in the project repository in fact).
Vendoring aside, this is also a useful pattern if you're "go:embed"ing a collection of build artefacts coming from another source, like a frontend HTML/JS/CSS project.
Sounds like an interesting problem to have. Would something peer-to-peer like BitTorrent work to spread the load? Utilize more of the networks' bisectional bandwidth, as opposed to just saturating a smaller number of server uplinks. I recall reading many years ago that Facebook did this (I think it was them?)
I vividly remember watching videos of the 2011 Japanese tsunami rolling inland. Seeing cars and bicyclists that looked like small toys that were completely oblivious to the torrent of water that was about to be upon them gave me such a sickening, helpless feeling.
I’m sorry to hear this, and you’re not alone (I’ve been WFH with young kids for half a decade so far). I know that feeling of pulling your hair out because the house is so _alive_ and distracting. Would you have any opportunity to go to a quiet workspace, a public library, a coffee shop, or return to an office part time? Best of luck to you.
In the mid 2000s, the wireless network infrastructure at my university authenticated your device based on SSH'ing into a server. But the specific SSH server used at that time did not support password-less logins via keys, so it required typing in a password every time you connected (and WiFi was flakey in that environment in those days, so dropped connections weren't uncommon). I asked the IT support folks about this, and they told me that I should try adding it to the software. I figured out what it would take and wrote some patches, but then they said they couldn't run something customized like that. Years on their reasoning makes sense, but at the time it was really disappointing and I dropped the effort after that.
I've never understood the argument that you should not optimize your own working environment (IDE/editor customization, alternate keyboard layouts, shell aliases, custom hotkeys, scripts, etc.) because it could be unfamiliar to someone else. I've also heard it in the context of, you shouldn't stray too far from the defaults because if you sit down to use a colleagues' computer, you will be out of your element. Unless your job is to pair program full time, or perhaps you're creating educational screencasts, maybe? If you slowly build out your own personal setup over time, presumably you should still always be able to explain what it is that you're doing at each step.
Thank you, I think that is exactly what I was looking for, and just what I had secretly hoped someone might suggest in response to my comment. Thanks again!
Thanks for mentioning the last major outage. That one was memorable for me as my son had just been born a few days prior. If that had happened the day of, I honestly don’t know how we would have managed it logistically.
Am I the only one who thinks that Git's UX is fine, and maybe even rather enjoyable? It has taken time to learn, and I am by no means a power user, but its model is now in my brain so, for better or worse, it's how I think and work now too (interactive rebasing for the win, all the time, and lots of shell aliases to shorten things). I do wish I had an easier way to split up a commit that accidentally included several unrelated changes though.
What's the lesson, that you can learn anything eventually, or that familiarity means you will lose the ability to accurately evaluate something?
If I ever see a resume or a job description that lists "C/C++", that's a red flag to me that either someone might not actually have that much experience, or someone doesn't actually know what they are looking for.
A practise I’ve found very fruitful in my programming journey is to do deliberate practise, even when (especially when) I’m knee deep in another problem. For me this looks like an explicit “learning” directory structure where I write short examples for myself, generally to explore an unfamiliar package/module, or to work up a simple but self-contained piece of code. I keep this separate from any other active project, and I often find myself referring to my own examples to refresh my memory, or use it as starter code for similar situations in the future.
I can still remember discussing the case while hanging around the student union office at school. I wanted to believe he didn't do it, in part because there would be a chance that the children might be reunited with their mother, and also because of a youthful naivety about the supposed honesty and integrity of someone of strong technical competence and achievement. I had been running reiserfs for years already by that point so I definitely had the "my team" bias. It's a sobering lesson that I continue to reflect upon to this day.
Has anyone ever stopped to consider the ethical question of applying the latest unproven fads of educational theory to unwitting students? Ideally before large scale rollouts?
As someone who grew up during a tumultuous time for the public education system in Ontario, Canada, it felt like ever year or two whole curriculums were thrown out and the latest and greatest "cutting edge" approaches and fads were foisted upon us. I can see a lot of parallels in software development, but I wonder about the specific potential for lasting damaging effects for children and young people. I know I experienced some gaps that took a long time to be addressed.
But were Go modules a better solution in that space? Should we have stuck with a less better approach (not casting a judgement on dep necessarily) just because it was an earlier attempt to deal with the same problem?
This reflects my experience as well. When I more or less know what I’m doing (where my typing is essentially the rate limiting step), playing familiar music helps me to focus, but when I really need to stop and think about what I’m trying to accomplish, I prefer as much silence as possible (I’ll even switch from headphones to large hearing protection earmuffs, the kind you should wear if you’re working with heavy equipment).