What craziness are you referring too?
686 karma · joined September 30, 2014
What craziness are you referring too?
Main takeaways from this article that I have also found are:
- Convert your most imported & core code first - it's much easier to convert files which only have TS imports - so start with those, and work out.
- Generating types for API response data has removed so many runtime errors. We generate types from GraphQL schemas.
While learning TypeScript takes time (but not much really), now I am familiar with it, I would code faster in TS than in JS.
When a new device is selected, the least recently selected device is disconnected. So once your first device is selected, start cycling again and select your second device. It's just a FIFO (First in first out) queue of devices.
First slide will tell you which device's are connected.
Subsequent slides will cycle through the device's in what appears to be most recently connected order. Subsequent slides cycle to the next device and when you hear the name you want, stop.
Once device is connected, you can cycle again to select a second device.
Also, since two devices can be connected at once, the device you least recently connected to will be disconnected.
It's super intuitive once you get the hang of it.
First slide will tell you which device's are connected.
Subsequent slides will cycle through the device's in what appears to be most recently connected order. Subsequent slides cycle to the next device and when you hear the name you want, stop.
Also, since two devices can be connected at once, the device you least recently connected to will be disconnected.
It's super intuitive once you get the hang of it.
- tell me the battery level when turn them on, and the batteries last for so long that they rarely get low enough for me to care what the level is.
- Have a button that cycles through which 2 devices are simultaneously connected. I can't imagine a system menu being anymore convenient than a dedicated button on my ear.
I wouldn't consider buying it unless it changed the deeper settings such as self voice level (I change this often while zooming). That's the only setting that doesn't have a quick shortcut physical button on the device.
So I did another recording to determine the frequency & bit depth, and then opened the dd disk image with those settings. It was pretty obvious from the waveform image which parts of the drive had the recording, and it was perfect.
Interestingly, I got those settings completely wrong at the start, and I could still tell it was music by listening to it, it was just very corrupted sounding!
The methodology of specifying your core dependencies, but also having locked version of your dependency's dependencies works really well.
AND you can easily export to requirements.txt if you prefer to use that in production.
Tasmania is also blessed in that Hydro is our "base load" which can be ramped up or down in seconds based on the fluctuating wind and solar generation.
I was driving past some of Tasmania's older dam's today on the way home from a hiking trip and I found myself trying to imagine what the river would have been like if the dam's had never been built. While I am thankful for Tassie's dam's and what they'll mean for our future, it's hard to not notice how much they change the environment.
> They are probably still burning lots of fossil fuels for heating and vehicle traffic.
Car's YES... although I'd say a LOT of people (perhaps most) heat with electricity.
On day 2, I discovered that I could spend hours lying flat on the couch with my legs propped up with cushions and a laptop on my 45deg legs. In that position, I could use the computer two handed for extended times as if I didn't have a broken collarbone.
Coming into the office to work (as COVID has been eradicated in my part of Australia) was harder since more than 20mins in an upright position (chair or standing) caused my shoulder to ache.
It took me a couple of weeks to work this out, but I ended up using a large upright shaped bean-bag as my office chair. I could mold the beanbag to give my arm support and sit the more reclined position that re-leaved aches. Having an Ikea standing desk helped, as I get into the bean bag and then lower the desk to match.
It's healed enough now to use regular chair and standing desk, but I learnt a lot about me and desk positions.
My main conclusion (after 15years of having a coding job) is that variation is key. There is no magic seating or standing position. Even if there was, it would be become uncomfortable eventually.
While probably the worst seating position for my back and posture, I have kept the beanbag chair at work, because using it occasionally feels good.
And, when at home I have continued to use the lying flat on the couch position, because again, it's different to how I usually use computers.
Which brings me to my main thought on this project (which I love the idea of): It's too permanent. I'm sure it'll feel amazing and comfy for a few days (or even weeks), but at some point for my body, it'd become just as annoying and uncomfortable as a regular desk.
Also, most states are now charging approx A$3000 for mandatory hotel quarantine, so returning to Australia is super expensive atm!
TLDR; I disagree: Django migrations are the best, and make reusable apps possible!
I've been using Django since before they introduced migrations and it was hell! Django only had "sync_db" then which would create your tables initially, but then you were on your own to write and run SQL manually for any model changes. This became especially annoying when using 3rd party apps, because if those apps changed the schema, you'd have to manually update your database for the 3rd party changes.
Then came along django-south which was a reusable app which provided migrations and solved all of the above problems. It became almost the standard approach, and third party apps often provided south migrations.
South became so popular, and was such a big improvement to the development workflow, that it's codebase was merged into Django (after making some significant API improvements) to become Django migrations. I can still remember having to covert all the files in the migrations directory from South to Django migrations.
Now we have a defacto standard of migrations work, and they allow easy use of customer SQL. Seriously, if you hate python based migrations as much as the author does, write custom SQL but put it in a Django migration so you get all the benefits of being able to rollback migrations etc.
Summary: when writing all of your own code for a single project then there is only minor benefits from migrations. But they are still worth it! In fact, I write lots raw SQL in my migrations, eg for constraints, triggers, notify, and just modifying my data. If I run SQL, it goes in a migration.
But migrations shine the brightest for reusable first and third party apps, which lets admit, we all use in most projects. This allows a single reusable app to be used for all projects regardless of database. Also, as a consumer of a reusable app, I can let migrations do their thing, and not worry if an update will break my database.
I guess it's all irrelevant when you don't use Node, aren't publishing libraries, and are compiling all JavaScript into bundles for deployment and never read the bundled code.
Compared to other "real" things, gold can be liquidated into dollars VERY quickly if you need to make a transaction, and since it's a real thing, it cant disappear.
Also, often gold is stored by the company you bought it from on your behalf, so you can sell it back instantly online. So no need to have to have a home safe.
Also, at an average return of 10%/year over the past 10 years (at least in australian dollars) it's has been out performing many other investment options.