{"id":127,"date":"2025-10-22T21:24:01","date_gmt":"2025-10-22T21:24:01","guid":{"rendered":"https:\/\/swaous.asuscomm.com\/blog\/?p=127"},"modified":"2025-10-22T21:24:01","modified_gmt":"2025-10-22T21:24:01","slug":"hills","status":"publish","type":"post","link":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/2025\/10\/22\/hills\/","title":{"rendered":"Hills"},"content":{"rendered":"\n<p>Much has happened in the last a-hair-under-two-months, and so I&#8217;m mostly writing this to unwind the ol&#8217; stack.<\/p>\n\n\n\n<p>First off: My first ever job interview was about a month ago. This is not, in itself, a particularly significant event. The significant part is that it was with Jump Trading, a fairly well-respected quantitative finance shop: apparently they found my LinkedIn profile, and liked it! I never had to apply to this position. Ironically I&#8217;ve never gotten an interview from a position I <em>actually applied to<\/em>: I start to doubt that applications are real at all.<\/p>\n\n\n\n<p>I (embarrassingly enough) did not ask for the name of the first engineer I interviewed with. Apparently they actually read my personal website(!) and this blog (!!) so, if you&#8217;re an engineer at Jump who had a fairly memorable interview with a gatech kid in September, thanks again for meeting with me!<\/p>\n\n\n\n<p>It was over Zoom. One would expect that I&#8217;d have gotten their name from Zoom: no such luck, it was a conference room Zoom with the name &#8220;Fearless Leader&#8221; and nothing else. There&#8217;s actually a really funny reason for that but I was under NDA when I found out, so&#8230; I promise it&#8217;s totally worth interviewing with them, even if all you get is an explanation for their naming conventions.<\/p>\n\n\n\n<p>Before the interview I bought a copy of <em>How Linux Works<\/em>. This was a good choice. I learned quite a bit from it, and indeed only knew the answers to several questions because of it! Apparently being a fast reader really is an ass-save.<\/p>\n\n\n\n<p>This interview was heavily luck-based; my technical skills are plenty sharp, of course, but what sold them was a quip about learning Linux from &#8220;a wandering tech shaman&#8221;. That was completely true. I actually did learn Linux from a wandering tech shaman and he actually did mysteriously disappear once I knew enough to go on without him. I did not expect that to go over as well as it did, but within 24 hours I got an email saying they wanted to fly me to their office to do a second round interview.<\/p>\n\n\n\n<p>I&#8217;m pretty young. Not, of course, young enough to be surprising to them, but sufficiently young that I&#8217;d never been on a plane before, never been to a big city apart from Atlanta before, and never had a job interview before. <em>There were a lot of firsts<\/em>.<\/p>\n\n\n\n<p>They scheduled for a little over a week out &#8211; <em>that&#8217;s not much<\/em>. Regardless I bought about a cubic foot worth of technical literature ranging from &#8220;pretty advanced&#8221; to &#8220;graduate level textbook&#8221;. I got through most of Fluent Python but barely even started OSTEP, Systems Performance, and DDIA, and I never even opened Linux Network Internals. Trying to read all of that in eight days may have been a bit too ambitious.<\/p>\n\n\n\n<p>(That said, I now know enough python to scare the shit out of professional python programmers, so there&#8217;s that!)<\/p>\n\n\n\n<p>Flying was fun! I&#8217;ve heard nasty things about commercial air travel but it wasn&#8217;t too bad. I&#8217;ll admit I freaked out a little bit when I had to confront my deep-seated unknown-known that planes do not work. The plane worked! Twice, even!<\/p>\n\n\n\n<p>Uber from the airport was absolutely insane; it took over an hour to get into the city. The driver was Russian, which was cool; we exchanged a few words but I really don&#8217;t know enough Russian to hold a conversation. That said: CHICAGO WOOOOO! The city was super nice. I expected it to be bleak but, aside from having no hills, it was a beautiful city. Coming from the southeast where it is pretty damn near impossible to see more than a few hundred meters in any direction what for all the hills: <em>being able to look at the horizon is cool<\/em>. Also apparently their streets have lots of trees! In Atlanta we pretty much always have a tree within view, so it was nice not to be in total isolation from the forest.<\/p>\n\n\n\n<p>The hotel I stayed in had a pillow menu. Like, an actual menu with the names of pillows you could have brought to you. I didn&#8217;t get one but I have a sneaking suspicion they were all the same pillow with slightly different names. I still occasionally start giggling about this.<\/p>\n\n\n\n<p>Interviews started &#8220;early&#8221; the next morning (around 9:00). I can&#8217;t say much about this part but, <em>Fluent Python helped<\/em>.<\/p>\n\n\n\n<p>And then I flew back home!<\/p>\n\n\n\n<p>Earlier today, I got the call from a recruiter saying I did not get the position. That&#8217;s okay. I don&#8217;t regret it; meeting the team was really cool and I&#8217;m incredibly flattered that they considered me cool enough to talk to me at all.<\/p>\n\n\n\n<p>That, in itself, is not sufficiently hectic to merit a blog post: events come in fucking packs.<\/p>\n\n\n\n<p>The week after my interview, it was exams. The week <em>before that<\/em>, (see: less than 24 hours before my interview), I had a lab in digital design. For this lab, we had to use a crappy crappy awful stupid piece of hardware called the &#8220;MyDaq&#8221;. In fact the name alone shouldn&#8217;t strike alarm bells; the alarm bells were fully struck for me one word immediately previous: &#8220;NI&#8221;. Yep. These things were made by NI.<\/p>\n\n\n\n<p>I&#8217;ve had a beef with NI since I was literally thirteen.<\/p>\n\n\n\n<p>Like, it should not be the case that this company makes hardware so bad a thirteen-year-old notices it, <strong><em>but they do<\/em>.<\/strong> The feud started with the RoboRio, a product decades before its time in the since that it cost\\ ten times more than microcontrollers with ten times the processing power <em>when it was released<\/em>. What is the justification for this? I legitimately can&#8217;t tell. The processor isn&#8217;t anything special. It supports a CAN bus, it supports i2c, it supports SPI, it has PWM output ports. Guess what else does this, and did do this well before the RoboRio was released? A FUCKING RASPBERRY PI. FRC has, as I hear it, moved to the fucking raspberry pi, because <em>even they realized how awful the roborio is<\/em>.<\/p>\n\n\n\n<p>Anyways.<\/p>\n\n\n\n<p>Having terrorized me in my FRC years, now NI was back to make my life miserable again. Consider the MyDaq. I never actually got my hands on one, because the gatech library was miserably undersupplied for the volume of students &#8211; something like a third of the class couldn&#8217;t obtain one. I saw from my tablemates, however, that it&#8217;s basically an array of digital pins controlled over a USB UART.<\/p>\n\n\n\n<p>The software bricked a bunch of people&#8217;s computers.<\/p>\n\n\n\n<p>Being a strict nonconformist and pretty good with Arduino Unos, I just built my own fucking daq in the middle of class. Credit to the professor and TAs &#8211; they took it completely in stride.<\/p>\n\n\n\n<p>It occurred to me while I was rebuilding the damn thing in a Chicago hotel room (the professor needed a video, and I didn&#8217;t have time to take one before my flight) that my life would be a lot simpler if I generalized: that is, programmed the Uno to take commands from some nice GUI software so I could do digital prototyping without jury rigging. Thus was born from my vengeance CircuitDojo. The idea is to make an AVR-based, fully open source DAQ that can run on the arduino uno lying around your desk. I&#8217;m actually pretty close to full digital functionality! Eventually I wanna support pullups, PWM, and analog pins, but those will be v2. With any luck the professor will officially recognize CircuitDojo on the next lab.<\/p>\n\n\n\n<p>There will be more posts about this.<\/p>\n\n\n\n<p>Anyways.<\/p>\n\n\n\n<p>A few days ago, I got a message from an old friend saying that, basically, the defense startup she&#8217;s working at needs a decent software engineer and my name came up.<\/p>\n\n\n\n<p>The company is very small and informal so the process was pretty simple, and now I&#8217;m contracting with them! And we have to ship completely novel weaponry on a serious big boy defense contractor level! In less than a year! It&#8217;s gonna be crazy but I&#8217;m pretty confident we&#8217;ll pull it off. Greater miracles, less time, the works.<\/p>\n\n\n\n<p>It&#8217;s not the big shift I was hoping for. Going to Chicago for an internship, and then hopefully working there full-time after graduation, would have been pretty much the best thing that could happen. But sometimes reality ain&#8217;t the best way it could be, and the only thing for it is to keep moving forwards. I still get to build cool stuff and work with cool people. Discrete math sucks and the MyDaq is terrible and this university is awesome and I still wear a balloon hat to all my exams and maybe someday if I&#8217;m super annoying there&#8217;ll be a course on Rustlang.<\/p>\n\n\n\n<p>Tonight I have to go on call with a defense contractor. And attend a Cory Doctorow talk. And finish introductory Java homework (and hopefully, if I have time, write some code hundreds of times more complicatedinteresting than anything in this course). But right now I&#8217;m just looking out my window. The leaves are still green, mostly, but red tinges are appearing. The wind is cold, perhaps not unseasonably so, but it&#8217;s still shocking. The sun frames the trees; soon it will set, and leave little more than the soft blue radiance that defines an autumn dusk. Hills roll into the distance, but I can&#8217;t see them from here. There are too many trees.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Much has happened in the last a-hair-under-two-months, and so I&#8217;m mostly writing this to unwind the ol&#8217; stack. First off: My first ever job interview&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/127"}],"collection":[{"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=127"}],"version-history":[{"count":1,"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/127\/revisions"}],"predecessor-version":[{"id":128,"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/127\/revisions\/128"}],"wp:attachment":[{"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/swaous.asuscomm.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}