Aaron Smothers

@SmothersAaron

Actively seeking new employment opportunities in Austin TX. AI practitioner and generalist coder. YC 2019. Very proud husband!

Vrijeme pridruživanja: listopad 2012.

Tweetovi

Blokirali ste korisnika/cu @SmothersAaron

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @SmothersAaron

  1. Prikvačeni tweet
    23. pro 2019.

    I'm publicly committing to the 100DaysOfCode Challenge starting today! Learn More and Join me!

    Prikaži ovu nit
    Poništi
  2. prije 17 sati

    As I go into next week I'll get my head out of the clouds of solving future problems instead of right now problems. This week I'm going to decide if a C/C++ implementation is needed for Android, or if I can get away with something faster to deploy. As always, thanks for reading!

    Prikaži ovu nit
    Poništi
  3. prije 17 sati

    For instance, I could see getting to play with both differential graphics rendering and some topology stuff to handle loads of different fonts. These are things I haven't used in programming yet and it would be awesome to have a clearly defined problem to work on with them.

    Prikaži ovu nit
    Poništi
  4. prije 17 sati

    OCR will have to wait for awhile, but once I get to it I should have come up with a few more raycasting/computer vision tricks to deploy. It's pretty exciting because it could be an efficient enough approach to be worth generalizing further.

    Prikaži ovu nit
    Poništi
  5. prije 17 sati

    I came up with the broad brushstrokes of how to do that. I'll likely standardize my inputs, similar to normal NN's and such. This will be a bit of a pain, but will be very rewarding when it comes time to do algorithm development.

    Prikaži ovu nit
    Poništi
  6. prije 17 sati

    I could use a similar approach to what I'm doing for object recognition for OCR. I mean, each character is just a single object. For my use case I only have to deal with one font in early versions, and a max of three total. The issue has been isolating the characters and today...

    Prikaži ovu nit
    Poništi
  7. prije 17 sati

    I had a breakthrough regarding Optical Character Recognition (OCR). In the first build of this computer vision app I'm planning to implement Google's on device ML Kit for document scanning. I've played with it before but I've wondered in the back of my mind if...

    Prikaži ovu nit
    Poništi
  8. prije 17 sati

    23/100 Not really a full day of "butt in seat" time, but I got some good problem solving in. Coding consisted of going back into some math and generalizing the hard numbers I used to originally get that part of the algorithm done.

    Prikaži ovu nit
    Poništi
  9. 31. sij

    Also, I think it's high time that I do a longer form public facing write up of the problem I'm solving and some of how I'm solving it. That way any of the wonderful people who are following along in this process will have a bigger picture view. As always, thanks for reading :)

    Prikaži ovu nit
    Poništi
  10. 31. sij

    environment, since I've got a growing TODO list, or go ahead and jump back into android. I've got a meeting on Monday that I would love to demo this at, and it would be awesome to do so via smartphone so I'll likely port my engine and algorithm over to Android.

    Prikaži ovu nit
    Poništi
  11. 31. sij

    I still need to do a small refactor to be completely done with the first test case, as I hard coded values in some of the math/logic for my sanity. Adjusting that to the general case will be straightforward. After that I will decide on whether to develop more in my Python...

    Prikaži ovu nit
    Poništi
  12. 31. sij

    Just a quick recap on what I've done to get here: 1. Built and tested the core raycasting function 2. Built raycasting control functions to handle multiple ray calls. 1 + 2 = a little raycasting engine. 3. An algorithm to identify a single MTG card and where it's title is.

    Prikaži ovu nit
    Poništi
  13. 31. sij

    22/100 It. Works! I've passed the first test case. That test case is an image I took with my phone and is not a perfect image devoid of tilt, skew etc. which means that I've built more robustly than I would have with a perfect test case image.

    Prikaži ovu nit
    Poništi
  14. 30. sij

    I will updating later today as well. My goal is to have the first "naive" success for the first test case, which is a single object in a stored image. I get to sit down for an interview with an interesting startup Monday and really want a working demo to share.

    Prikaži ovu nit
    Poništi
  15. 30. sij

    21/100 I fell asleep. Didn't update, egads. Two updates today then. Yesterday I implemented a new ray control function. The primary feature is that it takes a count int argument and returns the first count number of the target value. Very important for my algo.

    Prikaži ovu nit
    Poništi
  16. 28. sij

    Code and quality of code is impacted by fitness so I'll note here that I got two small runs in today. Also, I'm enrolled in another cohort of Y Combinator Startup School. I'm enjoying having a clearly defined product to work towards this time around, and the system is helping.

    Prikaži ovu nit
    Poništi
  17. 28. sij

    20/100 Set up that Trello board, defined terms for use in organizing the architecture with more granularity. Cleaned up the structure of my code base with a small refactor. Considered reuse vs overly argument bloated functions and have a working solution.

    Prikaži ovu nit
    Poništi
  18. 27. sij

    I think to complete this algorithm I'm going to throw all the steps into a Trello board tomorrow just to keep my sanity. I'm also sad to say that I've let my running lapse so far this year and the first 1/12 of the year is almost gone. So short run then trello task! :)

    Prikaži ovu nit
    Poništi
  19. 27. sij

    19/100 Worked on another function. This one takes the location provided by the function from yesterday and then shoots rays down vertically until they hit the target value.

    Prikaži ovu nit
    Poništi
  20. 26. sij

    Probably doesn't matter that much since I'm not being very clear with the over all project, but my internal compiler started throwing an error and now it's fixed :)

    Prikaži ovu nit
    Poništi
  21. 26. sij

    As soon as I sent this I realized that I had said something wrong in the first tweet of this chain. I'm not shooting rays "across" the x axis. I'm shooting them "along" the x axis i.e the rays are parallel to the x axis. "Across" sort of works but can lead to ambiguity.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·