Put the knife down and take a green herb, dude.
One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com
Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!!
Back-up your data and, when you bike, always wear white.
MarkUpDown is the best Markdown editor for professionals on Windows 10.
It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support.
Features you won't find anywhere else include...
You've wasted more than $15 of your time looking for a great Markdown editor.
Stop looking. MarkUpDown is the app you're looking for.
|Saturday, March 24, 2018|
TIL, Pokémon Edition:
I've been using Pokemon GO as an excuse to walk more (Apple Watch Pokemon GO app review: Don't.), and was wondering when should I evolve which of my eevees. You know, normal, grown up questions like...
That is, I didn't want to waste my candies on evolving the ones I have now if the next one I catch is likely going to be significantly stronger. But then what stops me from waiting forever?
And I don't want to evolve them too early if powering them up before evolution would increase their potential later. Etc etc. INACTION THROUGH INFORMATION DEFICIT!!!!1!
Determining Pokémon Apititude
I think that suggests that you might as well evolve first, with the chance to cut your losses if you really dislike their attacks after evolution.
Assessing the potential of each eevee is called appraisal. I'd seen this when I started playing, but had completely forgotten about it 18 months later.
There's great detail on what your appraisals mean here. Here's a taste for Blanche, the Team Mystic (ie, "Blue Team") leader:
It's apparently a lot easier to catch Pokémon if you can throw a half-way consistent curveball. From gamepress.gg:
That means a curveball with a Poke Ball has a better chance of catching a Pokémon than a straight throw with a Great Ball. Good to know.
How to do this? From eurogamer.net:
Also, here's an excellent YouTube on how to throw curveballs.
posted by ruffin at 3/24/2018 11:55:00 AM
|Thursday, March 08, 2018|
I think this signals less "whether iTunes LP was a bad idea" (though the skeuomorphism Jobs loved is slowly dying our from the `OSes) than "someone's paying attention to scaling down iTunes". I think they're slowly moving towards killing music sales, no matter what Sellers at AWT thinks. ;^D
I tried to think of why this is happening now, and believe it falls in with a general deprecation of non-Apple Music (qua the streaming service) features in iTunes. Here are a few data points...
The writing's on the wall. Heck, Apple Music on iTunes has a whole second UI...
After cashing in a $100 for $85 Apple Music gift card (<<< I'm not an affiliate, but it looks like it was legit), iTunes asked me if I'd like to put that towards an Apple Music subscription.
No, no I wouldn't. But I did drop into the Apple Music UI side of iTunes, which is obviously different than the normal iTunes Music Store. I bet there's some crossover with the Android app. After looking around the posh store of which I wasn't a member, I slunk out, knowing there's a new side to iTunes I don't get to experience.
Follow the money
The number will continue going lower. And subtract from that number the cost to support the mammoth mess that is iTunes and the iTunes Music Store. Microsoft's Groove is a small-scale test of the economics of supporting music sales. There are better places to spend that development time.
The Apple Music side of iTunes will eat the iTunes Music Store. We're getting rid of the cruft of the Store now. In a year or two, the iTMS will be a clear second fiddle to Music. Then we'll get a warning, like I did on Groove, to download all my purchases by a certain date, or they'll be unavailable.
And finally, acceptance
After years of hang-wringing, I find that by now I don't really mind that online track sales is dying. I have a good collection.
And I'm lucky enough to have a local record store. Here's what they wrote to all of their newsletter subscribers when Best Buy said it was closing down CD sales...
From Monster Music:
I don't see vinyl getting less hipster. And, as they say later in their letter, "Three, there will be a CD resurgence one day, you know there will. It might not be as drastic and fantastic as the vinyl resurgence, but I'll bet it'll be stronger than the cassette revival." That's probably a good call too.
After the iTunes Music Store closes its doors, I'll still have music to buy. And rip. And mix. And burn.
posted by ruffin at 3/08/2018 11:14:00 AM
|Thursday, March 01, 2018|
Oh google. Your raw source makes me something something.
Why is this in the page itself? Why do you need so much source to display your page? What ever happened to humans writing html code?
I know I sound like an assembly programmer in the land of OO, but it still makes me sad. ;^)
posted by ruffin at 3/01/2018 07:39:00 PM
|Monday, February 19, 2018|
If your architect hasn't written a tutorial -- not a cursory howto, but a tutorial -- you don't have an architect.
What does a tutorial look like? The canonical example for C# web apps, though now a bit long in the tooth, is NerdDinner:
If your architect hasn't taken the time to articulate their vision thoroughly, in plain, if expert-specific, [language of your locale], there's not much hope for your coders. Your codebase will necessarily be an unmaintainable cyborg (a topic I'm [not] surprised to find I've been ranting about since 2002).
The best job security is none. You've set your stage so well any competent programmer could come in and take over, getting up to speed incredibly quickly.
Those coders who work to ensure they're the most easily replaced are absolutely irreplaceable.
posted by ruffin at 2/19/2018 10:02:00 AM
|Wednesday, February 14, 2018|
I've been setting up a new greenfield project, and wanted to use not exactly a new stack, per se, so much as an "all-star" stack that'd capture the lessons I've learned coding recently. For me, that means it needs to be pretty straightforward, minimal dependencies, and minimal compilation. The fewer libraries and snowflake server requirements, the better.
On first take, after bypassing Node, which really is the winner,1 my guess was that my all-star stack would be...
VueJS was difficult to pick. I've used React, and almost solely React, for the last year. I like it. But I believe it contributes to monolithic source that's not necessarily factored well. The more interdependencies your code has, the more maintenance is an issue. And doing good React essentially requires, at this point, using Babel, and as soon as you're transpiling, well, the surrounding tooling and library dependencies skyrocket. Not to mention that debugging transpiled code either means you're wading into transpiler-generated muck, or you've got to maintain yet more tooling to step through things in something that's not the browser.
I was originally going to use Handlebars, which I've liked for years for its exceptional thinness & the way it encourages minimal business logic on the client, but caught Shawn Wildermuth on Jesse Liberty's Yet Another Podcast, and heard him talk about VueJS. VueJS is essentially Handlebars with, afaict, a few more recent lessons baked in. The syntax is actually very similar to Handlebars in many ways.
It looks like we've got good room to grow using VueJS' conventions if we want to do a full SPA in the future.
I also debated not using Bootstrap, but I don't think it's worth the time to roll your own responsiveness when Bootstrap does it so well. It's over 200 KB total, but if you have it cached, that's a one-time hit that's smaller than most images. You're fine.
jQuery was also debatable, since you can handle DOM manipulation fairly well by wrapping vanilla JS with some convenience wrappers to check for DOM existence, but at 69 KB? Come on. It's well known, rock solid, and has good industry support. Use jQuery.
I was going to go through my headaches setting everything up here, but I'll split that into a new post later. The quick version? Because of a wack nuget configuration I didn't realize was an issue (command line nugget didn't pick the "right" nugget server; I had a local one set up in VS2017 as well), I'm using SQL Server for now, though I will probably give PostgreSQL another look before I settle on a dbms.
1 If you want the cleanest stack, there's nothing more advantageous than using the same language on the server and the client. Node lets you do that. There's some overhead (learning & setup tedium) standing up a web server -- do you just use Express everywhere, or serve from Nginx? -- but nodejs is The Right Answer, imo. But I'm a C# guy "professionally", and there still seem to be more opening for C# devs than node, so I think there's an argument that a C# server-side should be easier for a customer to have maintained going forward.
posted by ruffin at 2/14/2018 11:10:00 AM
|Thursday, February 08, 2018|
And I do mean to resonate with Darwinism there.
posted by ruffin at 2/08/2018 11:56:00 AM
|Monday, February 05, 2018|
Have you ever opened frozen concentrated juice and had it look less juicy and more syrupy? I have.
After looking at it strangely for a few minutes, and remembering that it'd been in the fridge for months on months, though still well within its due date, did you remember that someone'd left the freezer door open overnight not that long ago? Boy, I did.
And that's probably what happened, confirmed by New York State's Department of Agriculture:
(Ok, yes, I'm mixing it in a growler. Unlike the Yankees, I couldn't find any pitchers.)
posted by ruffin at 2/05/2018 09:54:00 AM
All posts can be accessed here:
Just the last year o' posts: