381 karma · joined September 25, 2014
https://youtube.com/c/tutorialinux https://tutorialinux.com/ GitHub: https://github.com/groovemonkey E-mail: dave a@t tutorialinux @ com
20 minutes of me talking into the camera takes 2-4 hours to plan, outline, film, and edit.
30 minutes of screencast takes about 8 hours to script and film, and edit. The planning/research phase before that takes really long, because I try REALLY hard to avoid dependencies on jargon and specialized knowledge, to make the material accessible.
I'm actually about to experiment with a series targeted at more experienced sysadmins, where I can just improvise and work on a practical project without much planning or gradual explanation of the fundamentals. I'm hoping those videos will be much faster to create.
I spend a LOT of time thinking up and planning material, though -- not really sure how to count that.
I also made a poorly targeted and marketed practical system administration Udemy course last year, which does about $500/month.
These projects, along with a few other small things, are on track to make around $15k this year. That's after about 3 years of putting lots of time, effort, and love into creating content on YouTube.
Unfortunately that 'passive' income just barely approaches 10% of what I make at my full-time job (Sysadmin/Ops/Automation/DevOps? stuff), so the idea of working on my 'passive/hobby' projects full-time is not an attractive proposition yet.
I like building, running, and automating large distributed systems, so I'm not really itching to quit my full-time work and "just" be a teacher. The ideal situation would be 'regular' IT work 3 days a week, and working on YouTube, my own web apps, and additional tech courses the rest of the time.
ChrysaLisp is an Assembler/C-Script/Lisp 64 bit OS. MIMD, multi CPU, multi threaded, multi core, multi user, and will build from source in ~2 seconds on most OS X or x64 Linux desktops.
Maybe this will let me live vicariously through someone who has actually built the project I always dream of creating in my free time.
Others in this comment thread have convinced me to start actively promoting via e.g. Adwords, though. I'll start looking at that over the next few weeks.
More practically, I'm thinking about using something like Teachable for the next course.
OTOH at this point I've got content in a bunch of different places (YouTube, soundcloud, a website, udemy, packt/safaribooksonline), which makes leveraging all of these different platforms' features and supporting students there time-consuming.
Aside from work, hobbies, side projects, relationships, and other pesky human endeavors, I only have between 5-8 hours a week to work on tutoriaLinux. Adding another platform, with its own learning curve and features, seems like it might waste time that I could be investing into content.
I've actually spent a fair amount of time doing AdWords campaigns in the past, but I haven't done that for tutoriaLinux or the Udemy course yet. Maybe I should -- thanks!
Sorry, rambling.
I started doing Linux tutorials on YouTube a few years ago ( http://youtube.com/c/tutorialinux ) and then created a course on Udemy about a year ago. Affiliates make a decent percentage there (75%) but I suspect they have the same frustration that I do: Udemy has sales EVERY FEW DAYS.
Every few days there are sales that offer 90% off all courses, $10 courses, etc. etc. So a course with a $200 price tag will have an average sale price of $10-15, which leaves everyone (including affiliates) with pretty slim margins.
The simple problem is that they have the power to re-price courses as they see fit, and an incentive to do so (Udemy gets 50% of the revenue, possibly more from their promotions).
As it is, I make about the same amount of money from YouTube revenue (40k subscribers) as I do with one of the highest-rated Linux courses on Udemy (a few hundred dollars a month). It's really just a blip next to my salary; I can't see it replacing full-time tech work anytime soon.
When you're editing HTML/CSS, you don't have to run a deploy script before checking how your markup renders. Ngrok gives people writing web services the same convenience when dealing with requests from a 3rd party on the Net.
It is the equivalent of saving your HTML/CSS source files and instantly seeing the changes when you reload your browser.
I just wrote a little proof-of-concept Alexa app that crawls HumbleBundle ('Bundled Goods', very much beta quality at the moment) and ngrok was invaluable for developing it quickly.
I don't have a CS degree and don't have a clue when it comes to the "rebalance a red-black tree" stuff. In all of my interviews, this hasn't been an issue -- I can think intelligently about problems and solve them, ask questions, and show correct, well-documented, maintainable code that I've written in the past. I'm good with people and with translating between biz problems and tech solutions.
Even in a large tech city (Boston) with lots of well-funded tech companies, my experience has been FAR from the hell you'd imagine from reading HN. I think a lot of this just comes from the SV bubble overrepresented here. And maybe from the huge crowd of people here who, for various reasons, desperately want to get into one of the big 4.
Those few enormous advertising companies (G, F, A, etc.) represent such a small fraction of the actual work out there, and make so much of the noise, that it's hard to keep an accurate perspective.
Anyway, don't worry about it. It sounds like you'll have an easier time than me, and I've had it surprisingly easy during this whole process.
The thing that's more difficult to do on physical hardware, obviously, is scaling down every day if your peak load is some insane multiple of your base load for a 24h cycle. That's where AWS makes a lot of sense.
I don't think there's an obvious 'best' answer -- it depends on what you need.
It just bugs me that the current state of Ops/Infrastructure sometimes looks so much like the worst parts of the Javascript ecosystem.
It's a bit more complicated than running it on Windows, but still works just fine: https://tutorialinux.com/install-dwarf-fortress-ubuntu-16-04...
Enjoy!
If I had a nickel for every time I've said that...
Except FreeBSD jails are way easier to manage in terms of storage and networking.
Although I disagree with the need for Docker on FreeBSD, I actually agree with your statement -- Docker is such a popular thing right now that not supporting it will probably keep some people from trying FreeBSD.
On the other hand, the BSDs in general are communities where the Eternal September seems to be quieter than elsewhere. They're rock-solid and technically brilliant, but they're just not 'mainstream,' and not really trying to be. It bugs me sometimes, too, but I just don't think that getting more popular is what most people in that community are interested in.
It kind of reminded me of the old Asynchronous Transfer Mode protocol, with its cells.
Is it a failure to report income taxes at all? Or do you make so much more than $100k/year that the double taxation is killing you?
I'm just trying to figure out what, other than their already-reported income being audited, has got all of your expat friends so spooked...
The point you're making about tech startup costs is true, of course, although it looks like statistically speaking the chances of hitting it big are only slightly better than 'will become a famous singer' or 'will play for the NBA.'
But even if we assume that an average human with a laptop and AWS can now make it big, it seems like in the meantime so much of the other things that working-class people had going for them in the 1960s -- being able to support a family on construction wages, for example -- are gone.
Sooner or later you will trash your data unless you're using ECC memory (which the Raspberry Pi RAM chips are not): http://louwrentius.com/please-use-zfs-with-ecc-memory.html
For the record, I also think it's cool to get this compiled and running on RasPi; just wanted to add the ECC info for anyone now thinking of doing something with this in production :-D.
Perhaps loud suggestions like these are necessary due to a bias in the group that uses Docker. 20% people that really know what they're doing and have chosen Docker for a specific reason, and the hangers-on who try to emulate them by using the same tools.
Docker is an interesting, useful, and extremely overhyped tool. I may be wrong, but I feel like its popularity has caused a bunch of people who don't really need Docker to use it. Besides popularity, they can't really explain why they are using it over something like LXC or FreeBSD jails.
I imagine (again, no data to back this up) that this same large percentage of people are also the ones that just keep using the default Ubuntu image once they finish the "Get Started" tutorial.
I'm glad to see suggestions like this gaining popularity. If you're going to make the most of Docker, I think there's value to be found in really committing to the mindset of a 'purpose-built, no-frills environment for running a single process.'
From what I can tell right now, a huge number of people are using Docker "sort of like a VM but you need more of them, and Git is integrated and you have to tell it to do something or it stops running".
1. getting a warrant and running down to the book shop to ask them about what a single suspect bought, and
2. Having enormous amounts of data collected about hundreds of millions of people, processed and interpreted, essentially sitting in one place. Whether Google voluntarily gives it up or not is almost irrelevant (as we saw, the NSA is happy to tap Google's private fiber without their knowledge even when Google is cooperating on other fronts).
Of course the government will find ways to be evil if it wants (and I think that we're generally lucky because it doesn't seem to want to with any particular intensity). But that's not really the point here.
It's the difference between having many small, complicated little targets that each yield very little information, versus one conveniently enormous target that yields information on everyone.