#programblr

Our Fandom Cookies Digital Pack is now ready for immediate delivery 💨🛍️

For only $12.99 (LAUNCH SPECIAL), you can build your own fortune generator, decorate your devices, seek your fannish future...and get FREE SHIPPING.

At this point, the "Learn-Along" needs no intro! It's a:

🛠️ Fully-functional interactive site that gives you your own fandom-based fortunes

💬 Heavily commented code for beginners stepping up

🎓 Way to learn modern HTML, CSS, and JavaScript while playing with real code!

But wait— 👀

Inside you'll ALSO find:

🖼️ Wallpapers crafted by fannish artists

🌐 Website decorations and backgrounds

🎡 A printable Cootie Catcher for that nostalgia factor

And... 🚢 A FREE SHIPPING CODE for our store (up to $30 value!)

✨ Black Friday Special 🛍️

Jump in now and you'll get 1️⃣ Early Access to our future "Fancy" update, a step-up version of this project with even more learning 2️⃣ 20% off a FujoBoard THIS WEEKEND ONLY

💡 Shopping Gotcha: the FujoBoard discount and Free Shipping code don't stack. But that just means you can buy a FujoBoard now, AND get something new when we release our next batch of merch 👀)

Yessssss I finally got my fCC JavaScript developer certification :')

Of course they decided to go ahead and release a whole new curriculum a few days before I wrapped this up, thus making this previous version now somewhat obsolete (great timing, folks), but I don't really mind – I was only doing it to learn the skills in any case.

In my final project I got to work with APIs again, which I hadn't done in ages and always enjoy, and I got some practice with asynchronous programming.

um

one of the highest-voted answers was this:

I genuinely can't tell if it's a joke or not. I have so many questions:

Is this person... trying to channel Trump?

Why has no one else commented on this answer with some sort of observation about how weird it is? (the only comment is one suggesting Angular instead of React)

Just what?

What?

So I decided I did want to deal with the PDF problem.

I didn't resolve the large memory footprint problem yet, but I think today's work puts me closer to a solution. I've written a new custom PDF reader on top of the PDF.js library from Mozilla. This reader is much more simple than the full one built into Firefox browsers, but it utilizes the same underlying rendering libraries so it should be relatively accurate (for desktop users). The big benefit this brings is that it's a match for the existing CBZ reader controls and behavior, unifying the application and bringing in additional convenience features like history tracking and auto link to next issue/book when you reach the end of the current one.

The history tracking on the PDFs is a big win, in my opinion, as I have a lot of comics in PDF form that I can now throw into series and read.

Word of warning. PDFs bigger than a few MB can completely overload mobile browsers, resulting in poor rendering with completely missing elements, or a full browser crash. I'm betting the limit has a lot to do with your device's RAM, but I don't have enough familiarity to know for sure. These limitations are almost the same as the limits for the Mozilla written reader, so I think it has more to do with storing that much binary data in a browser session than how I am navigating around their APIs.

As far as addressing that problem, I suspect that if I can get TCPDF to read the meta data (i.e. the number of pages), I can use the library to write single page PDF files to memory and serve those instead of the full file. I'm already serving the PDF as a base64 encoded binary glob rather than from the file system directly. It doesn't solve the problem of in-document links, but since I provide the full Mozilla reader as a backup (accessible by clicking the new "Switch Reader" button), you can always swap readers if you need that.

As noted earlier today, the install script is still not working correctly so unless you have a working install already you'll have to wait until I get my VMs set up to be able to test and fix that. Good news on that front, the new media server builds much much faster than the old PI, so fast iteration should be very doable.

Anyone else understand modulo* as "Oh yeah like the Omer"?

*like division but with the remainder instead of a fraction.

So 10/3 = 3.3333...

To kick off this impromptu project (thanks to @cel-studies-stuff for the inspiration!), I am diving into the first of Lynn Root’s five project-based python tutorials available at newcoder.io. Project #1 is a data visualization tutorial, and it has been a somewhat challenging journey to get my computer set up right for this. Python 2.7 vs 3, virtual environments, symlinks, and cloned repos, oh my!

Desperately needed self-appreciation ahead – you have been warned!

I’m working my way through the fCC intermediate algorithms, and I just solved one SO fast and easy! It felt especially great because just a couple of days ago, I was stuck on one of the challenges for over 24 hours and didn’t really understand it even when I had completed it. But this one just makes so much sense to me!

It’s the challenge called “Missing Letters” and the very first thing I tried, worked! I honestly hadn’t even expected that. Normally I have to click “Run Tests” multiple times, interpret the error messages and try something else and add console.log() statements to test my code and so on. But this time I just slammed out that nice neat solution like it weren’t no thang. Didn’t even have to glance at the forums. I need to bask in this moment during an otherwise shitty month :]