I'm wondering if shifting frequency chirps like LORA uses would work in audio frequencies? You might be able to get the same sort of ability to grab usable signal at many db below the noise, and be able to send data over normal talking/music audio without it being obvious you're doing so. (I wanted to say "undetectably", but it'd end up showing up fairly obviously to anyone looking for it. Or to Aphex Twin if he saw it in his Windowlicker software...)
The issue is the (many) vocoders along the chain remove anything that don't match the vocal patterns of a human. When you say hello, it's encoded phonetically to a very low bitrate. Noise, or anything outside what a human vocal cord can do, is aggressively filtered or encoded as vocal sounding things. Except for DTMF, which must be preserved for backwards compatibility. That's why I say it would be creepy to do something higher bitrate...your data stream would literally and necessarily be human vocal sounds!
> and frankly I'd need to build a bit of a narrative to be competitive with other product hires.
Understand that just about _everybody_ is doing that.
You should avoid telling lies in applications and interviews, but you should 100% be "spinning" your experience to make it look best for there job you're applying for. You haven't "only done technical product work" for a year, you "spent several years dedicating personal learning time and took advantage of internal company professional development and mentorship, and eventually were promoted to technical product lead".
You'll need references who'll back you up on that, and it needs to be at least "true enough" that if they go and find co workers you didn't put down as references they won't outright contradict it. But most people can push the truth a long way in the direction they want it to lean without it being deceptive or outright lying.
This is true, but around here a lot of those jobs are what one of my professional circles calls "adult supervision", and I feel 30 is a bit too young to be targeting those.
Yeah. Lots of startup experiences is a good indicator of lots of technical war stories, and having been "that guy" or part of a team where a bunch of seemingly workable approaches to problems failed spectacularly is a _very_ valuable skillset to bring to the table with a bunch of fresh grads or early career devs. You probably need another decade to get the same sort of collections of war stories about managing people and teams and higher management, which is another skillset the "adult supervision" needs.
Having said that, I've seen teams of fresh grads and bootcamp trained devs, where some 30 year old adult supervision might have saved projects or companies from expensive or existential disasters. "No, we are NOT going to build this critical project's frontend on the JavaScript framework you and two of your bootcamp buddies spent the last 4 weekends writing."
Yup. I agree with the thoughts here. I just moved to a company as the Adult supervision role. I agree at 30 you’re probably closer to the “Lieutenant”, which is a role I’ve played before. I wouldn’t count someone out from playing a bigger part just on age though. I’ve seen plenty of hubris (most recently in the form of home rolling a Kubernetes/ECS alternative. Twice. RIP productivity) from people I’d describe as one year of experience twenty five times.
More than anything I think the OP just needs a change of atmosphere and even as an IC with technical management or a middle people manager somewhere stable he’ll have an interesting time with a very different environment.
The adult supervision guy is usually asked questions about the size of the teams they have lead in the interview. You get to be the adult supervision by having experience leading teams. You get to become team lead by being the best person on your team when the team lead leaves.
I have the same experience. But I'm running it on a NUC not a RasPi, which probably helps a lot.
Having said that, I have a Pi running HomeBridge to make a Pi camera and some non Apple Homekit capable IoT shit work with my phones/iPad, and I'm pretty sure the last few times it's rebooted were due to power outages, and I can't remember the last time I needed to even hit the HomeBridge web interface, never mind ssh into it. I'm a little surprised unscheduled power outages haven't borked the sd card, it's not even configured to do the ramfs overlay thing.
The thing is, though, the author learned some useful lessons about how new construction houses can be a bit unfinished. I'm sure when the next household task comes up, he'll sit down and look at every step of the task first to see if he can make any of those unknown unknowns, well, known, before he drives out to the hardware store.
I can certainly see someone at this point deciding it isn't worth the effort, and hiring people from then on, but some people (myself included) often enjoy the process of learning these things.
And this is the next step on the journey towards becoming a real senior developer...
> some people (myself included) often enjoy the process of learning these things.
A real senior developer knows when they're writing their own framework or library "for enjoyment", and when to just use the "boring technology" choice and work around any deficiencies it has for the task at hand.
I, for reasons nobody will wonder too hard about, have a downloads folder here with a few hundred Kindlebooks in .azw3 format. While non of them is quite as small as 91kb, many of then are around that 468kb size.
And they're whole goddamned novels that some talented author probably spend a whole year writing, not just single "small" webpages.
I’m a Fedora packager (not for this package). Like many others I have an unrelated day job.
If there’s an upstream complaint I might get to it this weekend, maybe next. If I’m busy for a few weeks that doesn’t make me stupid.
Have had my share of “discussions” with upstream who want the latest version packaged when this might not be completely in line with our guidelines. Not an uncommon issue.
Yeah it’s not fair to expect volunteers to show up on weekdays, I agree with you.
But equally, I don’t think it’s fair that packagers want to have it both ways. Packagers want to make subtle, possibly breaking changes to software they didn’t author. The end users feel the pain and complain to the author. The author has no control over the situation, and they’re feeling the pain during the working week.
So the packager has been instrumental in creating the problem with the patch, and when requested to do something about it, turns around and says “buddy I do this for free, I’ll get to it over the weekend, maybe.” Sure, but the author is feeling the pain right now.
Again, it’s nice that you’re volunteering your time for others. But it would be good if you acknowledged that the costs of packaging aren’t borne entirely by packagers. Authors bear part of the cost when they get blamed for broken software.
Sometimes changes are required to meet packaging guidelines, sometimes you can get exemptions. Of course users often don’t realise who’s done what.
I suppose my advice to upstream would be to direct the end user to the Fedora bug tracker, where the bug can land in my queue. Or advise the user to install from a different source.
The upstream that I’ve dealt with have been kind enough to lodge a bug themselves on the package I look after, which is also an option, and much appreciated.
> I suppose my advice to upstream would be to direct the end user to the Fedora bug tracker, where the bug can land in my queue. Or advise the user to install from a different source.
How is upstream supposed to make this happen when distro maintainers not only don't mark the package as modified by them, but also silently change the flatpak configuration so that installing packages from flatpak in the way that would normally install a clean upstream build doesn't do so?
I can, off the top of my head, name at least half a dozen of "those guys" and describe in detail the wreckage they left behind. Including one that was a major contributor to an 80%-of-the-billings client finding an alternative agency resulting in almost 100 people losing their jobs. :sigh:
reply