Thanks for this. Would love an annotated version of this if anyone is up for it. My C is pretty good, but some high level "what is being done here" and "this is what shouldn't work" comments would be cool to see.
> Developing on Android in Java is pretty gross, esp without rooting.
As someone who both writes mainstream Android/Java code and supports rooted Android devices on a daily basis, I would be most curious to hear a more detailed complaint.
Pretty much anyone who has so much as heard about seatguru will beg to differ! A few of the kayak / goog flights sites even display seat pitch in search results, now.
many of the enrichment routines are actually based around behaviours that are needed to better care for the animals. for instance, training a command to swim to a platform and breach up and present their underside? this lets veterinarian more easily perform examinations. training a jump to a particular side of a pool and staying there can let the maintenance crews work on filters after hours. modern enrichment routines have many purposes beyond entertainment, and if they can also draw paying crowds and donors, so be it for the better. a marine mammal specialist at your local aquarium can probably talk your ear off on the topic if you were to go ask about the "tricks".
primarily, we learnt by example and experiment rather than by query. to start we sought out every bit of sample code we could find in magazines, books, or usenet posts. we downloaded, printed, and read full manuals. when code failed, we tweaked every possible parameter and tested to see what changed. in a way, TDD was the (very manual) norm because it was the only option.
> one of the only large apps we know of which exists on all 5 platforms (iOS, Android, macOS, Linux, and Windows)
I've been evangelizing keybase for a while now and was checking almost every week for info on an Android app, but this 'existence' by way of a React app is a huge disappointment. Without a simple, lightweight, native app, it is very difficult to do verified builds and engage community contributions. I sincerely hope there are plans in place for a real Android app; I would happily contribute in any capacity I could.
I would definitely get tested for colour blindness. At least in the three cities where I have regularly driven over the last 20 years, the colours are distinctly different.
> Please make one amazing chat app. Just one. Merge Allo, Duo, Chat, Hangouts, Meet, Messenger, Voice, and your RCS platform into one extensible platform with third party integrations.
all of us who heavily invested in Wave are laughing so hard we are coughing up blood.
here at the downtown WF in Seattle, virtually every check out aisle has at least a few vials of homeopathic garbage. they also go quite hard in the pseudo science marketing against GMOs, gluten, and coconut / palm ingredients. apart from selling unreasonably priced produce of no particular merit, they are just another grocery store selling a particular brand of chemical puritanism and superstition.
out of frustration about speed, I actually look to switch away from Fx about once a year, but I always end up sticking with it because the extension and customization ecosystem just isn't there for any other option.
I read and generally upvote any novel work on ANNs regardless of practical use, because I feel like the ML field is still just as much art as science and inspiration begets creativity. At least for me, it might take weeks of experimentation before I have anything constructive to add to the discussion.
backend: Ninja framework behind nginx, because I can write Java in my sleep and it makes testing not-awful. prototyping is speedy and easy.
DB: Maria. again, familiarity is key. been using MySQL for almost 20 years and it does what I expect.
UI: nothing fancy. bootstrap and, if the use case absolutely requires it, jquery. have been going back to fairly js-light designs lately and clients seem happy for it.
PIPs are far more insidious than even that. sure, they are advertised as a way to get rid of bad apples or underperforming hires that slipped past the bar raiser. in practice, though, they are used by managers to further their own internal politics and goals as a no-fuss way of removing any existing employee that might make them look bad or be in the way of a friend they would like to get onto their team. all the manager has to do is give you a task with low visibility and then wait 6 months before calling you out as trailing in performance and bam, no way to defend your career. they know that most devs will just quit rather than put up with the bullshit or the humiliation. I feel terrible for the younger or less aware folks who don't see the process for what it is and take it as a genuine indication of their skills, talent, dedication, or worth.
headless machine with a low-wattage i5, 32g of ram, evo ssd, and an r9 200 gpu. I can leave it on 24/7 and ssh in from either my gaming desktop or my ultra light laptop or my android tablet. gradle / java / Android builds take about 12s on a warm package cache; the process is still storage limited, not cpu. the gpu has more than enough grunt to prototype and test ML apps. plenty of memory to keep a full ngnix / jetty / Maria / memcache running for client demos and still work on other stuff.
100% vim in a terminal (with gnu screen, naturally). it tends to be installed on just about every machine I am called upon to admin or work on. I even do day to day development in a term window because I like that when I shell into a server at 3am to fix something, it feels The Same As Always. I keep a fairly complex vimrc up on a public repo so I can have my config anywhere at a moment's notice.
I think I only chose vi over emacs (those were the only real options when I learned) purely because I couldn't figure out where the 'meta' key was. first big breakthrough was getting really good at jumping around files without a mouse. second big breakthrough was mastering multi window mode and keeping lots of buffers open like an IDE.
it might just be junk psychology, but I hate every IDE I have tried in 20 years because I can't tolerate the non-instant startup or the code not getting 100% of screen real estate.