Oh man that sounds fun (not setting it all up but doing it)

I think I know some guys who do bootcamps in SA if you want to talk to them. (In this case: Costa Rica)

There are other things to think about too. The best bootcamps do a lot of work on job/interview prep and actually make connections with local hiring companies. They boast good stats like percentage of students hired and starting salaries. To accomplish these things, you need to filter out some people up front a little bit.

probably a dumb question but why are there so many job listings for swift/android ? that means that companies are building everything twice? when would you only be building with swift or android? and what is the more valuable skill moving forward swift/android or react native?

I don't do mobile dev but everyone I know who does, does it with swift or android. If you think of all the plusses and minuses, react native loses in all of them except that you don't have to write 2 separate apps. However, even with react native for anything non-trivial you'll often have to have a lot of special case code for the 2 platforms, and will tend to include some swift or android code anyway.

After having worked extensively with osquery, another facebook "open source" project, there is also the big risk of facebook deciding to essentially take their ball and go home. In osquery's case, facebook decided to ditch the system they use to build osquery (make/cmake) and use their own home-grown build system, because it was simpler for them. Suck it, everyone who needs to build osquery on their own and now has to figure out how to do it the new system. They also essentially never accept PRs, don't respond to issues on git, and substantially break things almost every time they do a new release.

(maybe React has enough market share that these issues aren't present, I dunno)

Everyone either has legacy mobile apps or isn't ready to commit to non native yet. We have immeasurable trouble hiring mobile engineers so it's actually a super good skill to get for jobs or consulting

How do you find osquery itself? The data model seems absolutely bananas.

Anything that is not in daily use by facebook itself is almost guaranteed to be broken. I've had to fix things that don't work even a little bit, and hadn't worked for many many versions, and either no one notices or no one cares. Like early in the 3.x releases, syslog_events stopped working (they switched from one libc++ library to another and it busted during that). Their AWS implementation broke similarly when they updated the AWS client library and no one ever fixed it. Their file events implementation is broken onl inux if you try to combine it with anything else that uses inotify. I have a long ****ing list of stuff that's broken. I used to post to their github and submit PRs and stuff but basically I never heard boo from anyone, so we just forked and deal with it.

It has major performance problems. *Really* major problems. In our use cases it really only works on very trivial use cases, you have to be *extremely* careful writing queries because the underlying implementations of the "tables" could literally be anything, like when you select from a table it might do something very slow, and if you use a where clause like "where foo in (a, b, c, d) it might literally refetch the whole data set for each in clause, etc.

The watchdog system is hot garbage. It's level of configurability is low, it's reporting is terrible - for example if it's in the middle of running a distributed query it'll just die and never even report back that it gave up on the query.

In a technical sense it's very interesting and on a surface level it seems great but once we really started trying to use it to do real work it fell apart. Unfortunately we have it installed on like 50-100k machines and we're pretty much stuck with it so we're trying to fix problems as we find them.

I'm starting to think maybe I'll try to teach programming at a high school somewhere in Latin America. Like I said I don't need much money and it would be hugely rewarding.

I could make extra money by tutoring local rich kids in programming.

I've always been pretty loathe to use stuff like this, but a friend wants a store online and I put it up in Wordpress. Wordpress is actually pretty sweet. I did get to do a little programming in python to fix up the distributor's excel list of products and images before importing them. I know Wordpress "developer" isn't the most respected line of work, but it might not be so bad.

Combination Solar and Programming school in Antigua Guatemala?

People love to rag on PHP and Wordpress, but i have some consultant friends that are mighty good at both and make a lot of money. They also actually enjoy it!

Yeah - they have 300+ days of sunshine a year and it's at 5000 feet - so very clear air. Well except when the nearby volcanoes act up - which is often.

Rusty, thanks that’s interesting. I’ve heard some similar stories (but definitely not as bad) about Presto. But Presto seems much better organized and structured so it’s probably easier for them.

I complain about it a lot, but there's probably not a real alternative that's any better. The biggest problem is that the team supporting the product we base around osquery is... tiny. When you have as many people running something as we do, a 1 in 10k installs problem happens daily

Yes, companies are basically building everything twice. Usually they also build it a third time for web/mobile web too. For bigger companies with either a lot of users or a lot of revenue, the extra work is easily justified. React Native is probably suitable for less widespread use cases with hundreds or a few thousand users. Even in those cases I would use Flutter instead.

What I often find infuriating is when a website and a phone app have substantially different features. Like, oh, if I want to do this particular task, I HAVE to get my phone out? Even though I'm already on your site? WTF?

lots of people talking about flutter now but i just don't see any job listings for it around here.

You and me both man, but I have learned that is just because we are Olds. Everyone does everything on their phone. I hate doing anything on this tiny ass thing with no keyboard

I used to hate doing stuff on my phone but now I can type nearly as fast as I can on a keyboard

I can type as fast on a phone as a keyboard. 3 out of 4 letters are wrong. But I can do it.

The reason for this is because everyone runs ad blockers on traditional web. If you can convince your users to download the app, you can serve them ads. Reddit is a good example of this.

I think the feature disparity goes the other way often enough too, though, someone will have a feature on the website that is better than what's on the phone app.

From working at places with a lot of app usage I would say that it's mostly because the teams are completely separate, don't talk to each other, and no one is really a big user of the app and/or the website so they don't notice or care.

Here's an example that goes both ways:

On myfitnesspal if I go to add a food item to my "diary", if I start typing it will show me matches for things I've added in the past, which is really nice. The app does not have anything like this.

But on the website, there's a "frequent" tab that has the most common items *from recent history*. The app has a "frequent filter" but it appears to be for all time so the #1 and #2 item on the list are both things I haven't eaten in 2 years. In fact 7 out of the top 10 I haven't eaten in a year. So the "frequent" tab is more useful on the website.

But really it isn't even so much that one is better, it's that they're different for no reason, so if you use both at all, you have a higher mental load than if they were just basically identical.

Also, a *shockingly* high number of people do not use *******. Even among tech people adoption is not as high as you'd think. How did I learn this? I sometimes forward colleagues pages from 2+2 and they are like WHAT HOLY HELL IS THIS IT'S COVERED IN ADS! And I'm like, really? I had no idea.

My coworkers willingly watch youtube ads. For god's sake, why.