Skip to main content

Summer Break 2017, Day 4 of 83: Short notes

What did I accomplish today? I finished my lesson on naive Bayes, learned about linear dependence, and began learning about graph-based algorithms.

Because of my unfortunate procrastination and a request from a family member to do some unexpected work, don't have too much time today to document my experiences. I'll likely produce a follow-up or two on Saturday to compensate.

Other news

Today, the third developer preview for Android O came out. I've been reluctant to join the Android Beta Program, though. My Nexus 6P already dies around 40%, and I don't want to tempt the gods of battery life to increase that number. Sure, Android Nougat already introduced improvements to Doze, and Android O will put background execution limits for services, but I know the real problem is likely the hardware. Because my phone is from Best Buy, and my benefactor didn't get extended warranty, I'm essentially screwed until I get a new phone. (Hopefully, that new phone is a Pixel 2 that I receive for Christmas, but I'm not too optimistic about that.)

On a side note: I really despise the new emoji. I've confirmed it's not just because they're new; the icons go against everything Android stands for, and, based on a quick questioning from my family, the old icons actually appear better to the eye. I'm disappointed the Android emoji designers aren't taking the philosophy of "Be together, not the same" to heart. I don't want an Android phone to use iOS emoji. I want Android's unique brand identity to show through.

My decision: I'll wait until next week for any blaring issues to surface, and then I'll give in to the terrible cat emoji.

I have some data to sift through and manually input onto paper. Have a good night.

Comments

Popular posts from this blog

Countdown to I/O

This is going to be the second year I've witnessed I/O live(streamed), from school, nonetheless. While I'm hoping Google announces some bombshell that is going to give them some massive monopoly, I, containing bouts of cynicism inside, expect a bit less. Firebase, Firebase When Google announced Firebase last year, I shook and shivered with excitement. I thought, "An integrated mobile and web development backend I could use to make anything? Sign me up." Of course, Firebase got better with new features like Cloud Functions, but I don't think Google is done with it - they're not even close. While I know just as much as anyone not at Google about the announcements to take place in less than five to six hours, I'm sure Google is going to announce more integration with their Cloud Platform. Cloud Functions was the beginning of Firebase adding functionality to a "consumerized" cloud, if you will. The rest of Google Cloud Platform will be for anyon...

What's a TSI Test?

I took the TSI test on Wednesday, but I wasn't the first one in the lab to finish. I blame my proctor's slowness at informing me on some prerequisites that Administration didn't inform me about and my own apathy to a test that didn't seem to put up much of a fight. Three other people beat me to the punch, but I still managed to finish before the end of third period. Since this test doesn't involve a non-disclosure agreement that people really don't care about anyway , I'll talk about the contents of the test. There's nothing too interesting about the test. I likely could have gotten a perfect score if I tried, and that's not just me being cocky. There was no advanced math on the test (nothing higher than algebra), but the reading sections are slightly more comprehensive than the STAAR test's. I literally mean slightly more comprehensive; the STAAR test is more fiction-oriented while the TSI's reading (I think) only consists of nonfiction pas...

Summer Break 2017, Day 5: How Hard is it to Upload a Photo to Firebase?

God help you if you ever decide to implement camera functionality in Android. I didn't have much planned today, but thank goodness I didn't. The Setup Here's the dilemma: I wanted to make a very simple app that will let me take a photo of text and have it read out to me. Using the Google Cloud Vision API ,  I can essentially scan documents and listen to their contents instead of having to use my eyes and scan the thing. It will be great for accessibility and so on, but the thing is I can't have the Cloud Vision API scan documents that I haven't taken. I want to do processing in the cloud to model common app architecture and to reduce strain on the client app. Here's the service flow: Client app takes photo Client app uploads photo to Cloud Storage for Firebase Cloud Functions scans the document for text Cloud Functions updates Firebase Database with scanned text Client app intercepts database update Client app speaks text from database The Co...