Take a look at Standard Ebooks[1] as well, which I heard from here at HN. Their motto is "Free and liberated ebooks, carefully produced for the true book lover", and they live up to that standard.
Libgen like Project Gutenberg often has poor formatting on eBooks. Librivox recordings are donated by volunteers. A single book might have multiple readers. Not ideal but you get what you pay for. Audible also has some classics for free, with subscription.
Kindle ebooks though they are hard to find by design, I think. Amazon wants you to buy stuff, even when the work is in the public domain. There is also, of course, Project Gutenberg [0], but I have not tried to interface with that project through ereaders. I wonder if anyone reading this has any additional tips :-)
DevOps isn't exactly an ancient field. I know you said you're already junior heavy but even if building someone up takes you six months you're going to likely be better off in the meantime than trying to find someone able to produce the value you need from day one.
My employer is also having trouble attracting senior frontend devs right now and our take seems to be that there's a lot of competition for good candidates, that's unlikely to change in the short term.
EDIT: Not to doom, but times are changing, might be worth evaluating if you really do NEED a senior. A lot of the way people look at used cars, and housing, (and gas prices), and remote work has changed in the past few years. Maybe easily acquiring senior devs is something that is also changing.
Seems like an opportunity for a carseat product that sends your phone a push notification when you get out of range if it detects a child in the carseat.
I am largely ignorant to license law so forgive this probably basic question
If the idea of public domain is clearly established in law should it not be enough to have a license file that simply reads.
Everything in this repository is public domain, all contributions to this repository are public domain.
Obviously if someone were to submit code stolen from a project under another license it would create an issue. But the same could be said for any project.
The concept of 'public domain' in the sense of all legal property rights and responsibilities being relinquished is not clearly established everywhere, and where it is, it sometimes applies only in certain circumstances (like years after the death of the creator).
Porting the mobile port back to PC is one of my biggest complaints with remasters. Final Fantasy on PC went that route and I would honestly rather pay Square $15 for an emulated version then the releases we got.
The new 'pixel remaster' games Square is putting out have been great so far. Standardizing on a 16-bit sprite style, new music arrangements, and widescreen support. Only issue is the English font choice, but if you're on PC that's easy enough to fix.
So how do you convince other leadership and the people you lead that this attitude is better?
I've had folks on both sides of the fence who feel strongly that hierarchies should be absolute and following top down decisions is more effective.
This article isn't about how to structure your organization, it's targeted at people who are thinking about how to be more effective leaders.
If the leaders in your org are crap, then your org is lost no matter whether it seems to have a flat or top-down structure; but if you're already in charge and thinking about how to make things work better, the lesson of the article is to be clever about it, rather than defaulting to the dictatorial mode.
I think the Paradise Lost analogy is about effectuating top-down decisions while making them appear to be consensual. A contemporary version can be found in the Hegelian Dialectic.
Bob Gurr, a famous Imagineer, said of his boss Walt Disney, "Walt was the greatest dictator ever. People went along with him because he was always right."
Whether actually right or not, Steve Jobs and Elon Musk can be said to have had this effect.
moreso, a strong hierarchy can work when constructed meritocratically (the benevolent dictator concept). the (very) hard part is figuring out what's the most meritocratic and how to encourage that construction. most hierarchies end up unmeritocratic due to endless political machinations to subvert that definition and construction.
and to be right, you can slap the puck to where you want to go, or skate to where the puck will be. good leaders do both, and much more, like communicating early and often and using various commitment devices (e.g., cutting off retreat). there's really no trite summation of good leadership.
https://store.steampowered.com/hwsurvey/Steam-Hardware-Softw...
Looks like linux barely beats out macos