Home Artists Posts Import Register

Downloads

Content

Hey everyone!

I hope you're all doing OK, as I scramble to catch up to the infuriating Linux Mint Team who apparently couldn't be bothered to communicate a precise release date for Mint 21, and are forcing me to re-jig my whole publication calendar for August...

Here is your new, fresh episode of the patroncast!

In this one, I talk about:

- 01:13 Do Linux DEs need updates / reworks / redesigns to be good, or could they just stay as they are and still be perfectly usable?

- 09:55 Painting myself into a corner, as in "there are other things I'd like to talk about but I would be considered a sellout if I did"

- 16:38 Analyzing the proprietary software I still use, and whether I could replace it with a FOSS alternative or not

I hope you'll enjoy listening to this one!

Best,

Nick

Comments

Emil Johansen

If you want to cover more content then you've already taken the first steps by going full-time and optimizing your flow to maximize output at sustainable levels. You've already identified that the wrong steps to take after that would be to scale unsustainably or diluting your content. The primary issue there is not one of losing credibility (measured by YouTube and Twitter comments, no-one has any of that anyway), but the jack-of-all-trades-master-of-none effect. If one can't come to your channel for sufficiently in-depth coverage of certain topics then it's a way more general purpose one and you would at present be significantly out-gunned in that market. Healthier further steps would involve taking on collaborators. Not partnerships or podcasts lasting while the personal interest of the involved parties, but straight up fixed roster collaborators. That can very easily be made to sound scary in an "omg I need employees now, but taxes!" way, but you have indicated that from both earnings and under-charging advertisers you currently have flexibility in the company budget which seemingly should be able to cover the contracting rate of someone spending an amount of days here & there. Fixed collaborators allow you not only to scale without wearing yourself down, but also get to a point where a collaborator initially establishes a specialty, marking this person as "the host of X content", after which you yourself can also do content on X every once in a while as a "Nick guest-covers X today" - not labeled like that, but perceived and understood without implications of dishonesty or whatever. And since the only concern is viewer opinion then who cares who actually does the research and other legwork on a piece of X content? That doesn't generally show in the final video and you get to still mess with X like you wanted to. Obviously taking on a collaborator isn't additive-only. You surely recognize that there will be overhead even when you cut away the employer-employee setup by having a client-contractor relationship. So you would need to reduce your current workload a bit to compensate. Perhaps the news videos would be a good candidate - moving yourself to a position of collaborating on the links collection document with the collaborator and then they write the actual script, do the recording and editing, and you just do a final pass & upload. Would seem like both a good first step for the collaborator and a decent chunk of work off your shoulder for that overhead and a bit?

Emil Johansen

Re: Often changing DEs: Recall these are not businesses, but organizations of enthusiasts. The effort is generally going to go where it wants to and as a rule it is easier to sell a developer on the prospect of working on a massive bag of bugs when they have the prospect of also doing something more shiny. A project trying to enforce "no shiny" or whatever is one in the process of shutting itself down.

thelinuxexperiment

I have to love how you swoop in with extremely accurate, business focused decisions that I couldn't come to on my own! Thanks a lot, I feel that this would, indeed, be a good step, if only to automate as much of the Linux news video process as possible, so I could get a bit more time to work on other topics, and, at most, maybe even have "guest hosts". I would also probably like to work with someone again, it's cool to be a one man operation, bu having colleagues is also pretty cool...

thelinuxexperiment

Oh yeah, absolutely, it was more of a general reflection on "if taken out of every other consideration, do we really need this". Obviously, these projects are run by enthusiasts, and having some new, shiny, or better ways of doing the same things is more exciting than ging "full maintenance mode"!