Showing posts from April, 2013

ChatGPT - How Long Till They Realize I’m a Robot?

I tried it first on December 2nd... ...and slowly the meaning of it started to sink in. It's January 1st and as the new year begins, my future has never felt so hazy. It helps me write code. At my new company I'm writing golang, which is new for me, and one day on a whim I think "hmmm maybe ChatGPT will give me some ideas about the library I need to use." Lo-and-behold it knew the library. It wrote example code. It explained each section in just enough detail. I'm excited....It assists my users. I got a question about Dockerfiles in my teams oncall channel. "Hmmm I don't know the answer to this either"....ChatGPT did. It knew the commands to run. It knew details of how it worked. It explained it better and faster than I could have. Now I'm nervous....It writes my code for me. Now I'm hearing how great Github Copilot is - and it's built by OpenAI too...ok I guess I should give it a shot. I install it, and within minutes it'
Above is an activity's lifecycle. Twitter auth only works if the time on the phone being used is correct.  Sometimes the emulator is way off and then I'll get an error when trying to get authorized. Twitter resources:
OAuth works like the above.  What makes it REALLY difficult to do in android is the constraint that you can only make external calls through an async task (a new thread).  One way to do it with Twitter4j is to setup the Twitter object reference, AccessToken and the RequestToken as globals (ew...) and then use 1 private AsyncTask to call twitter to get the request token, then show the authorize url that's returned so the user can go authorize.  Then ask the user for the verifier, and use it to start another asyncTask to get the accesstoken. 

android tips/notes

APK = Java (src,gen) + Resources (res) = glue between Java and Resources make a project command-line compileable : enter project workspace directory > android update project --name --path . > ant install ( will fail if no device to run on) > ant debug (should succeed, as it only compiles a debug version) info for android virtual machines located in ~/.android/avd/ adb (add sdk/platform-tools to PATH) adb shell adb devices, adb -s To get nexus one working : edit /etc/udev/rules.d/51-android.rules and add SUBSYSTEM=="usb", ATTR{idVendor}=="18D1", MODE="0666", GROUP="plugdev". then unhook phone, and restart everything, then allow debugging on phone, and hook it in and then start eclipse .... that seemed to do the trick 18D1 is the vendor code, i believe for google - don't use the htc one.                              Services : code that runs in the background (no UI) Content Providers : share content with applications across ap

android setup

Download the adt bundle, then use to start your first app. Might need to get a device to test on.  Also might need to get the right libraries. Always start eclipse using ./ eclipse - vmargs - Xms1024m - Xmx2048m ( reference : ) AFTER doing all that, you can try using ruboto :