Same. As an American living on the Canadian border most of my life, I learned most of my Candaianisms from factory coworkers and AvE's youtube channel.
Could be worse, and be like me, who instantly looks up any word he doesn't understand, and because he does it so often, forgets the definition almost as soon as it is read after moving on.
It probably takes me a good seven to ten times of looking up a new-to-me word to really nail it down. As a result, a lot of my blog/personal writing is filled with odd phrasings of things because I never quite learned the prescriptive way of using said word.
I have a different take on permission license. I offer up what little code I produce under the assumption that anyone can use it for whatever, just give me credit. Why? Because it might result in an interesting collaboration on a project I like. If someone uses my existing code to accomplish something neat and sees who I am, they can reach out to me for more, which I'm open to since it would likely result in some growth for me as an amateur. I'm not particularly interested in making money since I recognize that I am nowhere near that level, yet, but creating a future opportunity seems like a good idea since I enjoy coding.
True, but while there is a decent sized Flipper Zero community, I found it to be significantly smaller and less prone to fresh development than the other two you mentioned by comparison. The Flipper Zero is stunted by a good portion of that community being individuals who want a pocket hack toy without having to do any work to make it go, resulting in perceived stagnation of the device.
Perhaps I missed something when I owned mine? So many people I encountered in said community really just wanted a wifi deauther, which could have been built or purchased in a variety of cheaper ways. I got bored with it quickly, and returned to doing interesting things with Arduino and ESP32, but YMMV.
I also like Mudlet and KildClient, but it's really best of you try a few and decide which works best for your tastes and needs. Blowtorch is still the go-to client if you want to play via Android mobile, last I checked. And you can always just straight up connect via telnet/ssh using your favorite terminal emulator if you want to keep things really simple and exercise your skills with graph paper.
But if you do not hold the engineers accountable for reading the memo, that's on you (or whomever has the authority to do that). This is why having things in writing is important and verbal directives have about as much value as a fart in the wind.
I don't know about anyone else, but contrary to my general disdain for meetings* I have found product owners/process managers to be useful in the regard of having one central person to funnel things through on a particular project. The bottleneck also creates a nice buffer of accountability in both directions and they typically offer either new or refined SOPs after solving the same problems over and over again. Plus, they can sit in on the meeting while I go do something useful.
I may just have been lucky with the few I've had to work with though, so your mileage may vary.
*or as the song says, a little less conversation, a little more action please
I have to disagree since I can also just not listen/pay any attention to what is vocally delivered in the meeting, which I find to be an abhorrent waste of my time in the first place. If the directive is in writing such as an email I (or the person who issued it) can't point to that and say "you did not read this" which shifts the onus entirely on the person receiving the directive.
About a year ago, I nearly quit my job over this, going so far as to put my two weeks notice in as a way to hold a gun to their head, repeating my frequent request that all directives handed down from on high _must_ be in writing if they are expected to be followed. My company had (still does, to some degree, but we are still working on it) a cancerous culture of he said/she said that was being abused to avoid any accountability from upper management, which was both impeding the actual work being done as well as demoralizing to th workers. We even ended up losing some talent over it before I used my own value and authority to put my foot down, making me wish I'd done it sooner.
Verbal directives only stroke the ego of the person delivering them and their meaning either evaporates or gets twisted as soon as everyone walks out of that conference room or logs off that video call. If the person issuing them is not willing to have their directives questioned when they are in writing, then they should not hold the position they do. It's not about questioning someone's authority, it's about ensuring the directive makes sense with the work being done and adds value or guidance to the existing processes. Screw the fragile ego nonsense.
Fair point in your case, but my experience across companies and industries is that people just don't read. It's true in any customer facing experience where tutorials etc are routinely unread and ignored, it's true for execs who are always short on time and want the exec summary in order no to read a whole memo (however misguided this may be in certain instances), it's true for seasoned professionals who prioritize and decide to ignore certain requests until they are clear enough / repeated enough, the list goes on.
Even people getting @mentionned on slack or in emails seem to find it acceptable to say routinely they didn't see/read whatever it was they were specifically asked to look at.
You're right, and that tracks with my experience too, sad as it is to have to admit.
However, if you're not holding people accountable for not reading the directive/memo, then that's on you. When you have something in writing that you can point to and say "look, there it is, I provided you with the information, you chose to not acknowledge it," it's very damning to the person who ignored it.
Without getting into details about the time I nearly left my company, I can tell you that one of my greatest weapons was (and still is) being able to literally recall emails, SOPs, and SMS messages that had been ignored. It makes me a thorn in the side of lazy managers and legacy hires that turned out to be freeloaders in my industry.
The people at the bottom of any organization have a responsibility to hold the people at the top accountable, just as it works the other way around. This is extremely hard for those of us near the bottom of an organization to do, I know, but if we don't, we are giving permission for the problem to persist and make our work that much harder. We all know that managers and those above them will avoid doing as much work as possible at any given time, but willful ignorance is not admissible in court of law, so why should it be any different in the work place?
This matches my experience, with email in particular every organisation I've worked for it's been normalised that it's OK to not read every email, particularly if it's long or detailed. Clearly if the CEO emails you alone about something important that doesn't hold but for the vast majority of emails it was seen as acceptable to not read them and to even openly admit that. I remember being phoned by a department head once asking what an email was about - they weren't going to read it until I explained why they should.
It's a side effect of the information noise we're all subjected to, if we all received 6 messages a day we'd probably read them all but as we often get hundreds (thousands if you're getting automated messages) it's "OK" to miss a few.
The problem is interpretation. The key phrase is "interference with privacy" which is ambiguous yet all encompassing. You say it says nothing toward solicitation or manipulation where I interpret both of those acts as "interference with my privacy." Not saying your version is wrong, by the way, just different from mine as a example of where the protection falls apart.
My gut feeling as that no matter how much additional and specific language we add to any bill of privacy rights, there will always be holes or work-arounds due to interpretation and semantics. This is how lawyers in most robust legal systems make their living, after all. The data that results from robbing us of consent, privacy and agency when engaged with websites, web/mobile apps and software is so insanely valuable that the people interested in collecting and selling it will be happy to keep one step ahead of whatever language we come up with that attempts to mitigate their actions.
We need a different solution, one that returns us to the levels of implied trust I remember from the late 1990's/early 2000's Internet, one that prevents corporate entities from being the dominant drivers behind its growth and development. However, I am not technical enough or imaginative enough to even guess at what that solution might be, so from my perspective, the battle is already lost and we are at their mercy unless we avoid having an online presence as much as possible...a bit like that old classic movie War Games, the only way to win is not to play.
> My gut feeling as that no matter how much additional and specific language we add to any bill of privacy rights, there will always be holes or work-arounds due to interpretation and semantics.
Nobody will ever write a perfect law and you’ll always see cases like dark patterns when people try to unsubscribe from things or try to maintain their privacy, until there is proper enforcement and businesses start getting punished for violating the intent of the law. That is also unlikely.
https://www.youtube.com/arduinoversusevil/videos
reply