Edit: Also, I guess weight also of such a battery, but I suppose maybe the weight can be understood by how much reserve it would need.
4,075 karma · joined August 9, 2015
if you really want to write me for some reason, stallmanniquin at gee mail dort corn
I don't check this often though so please don't be upset if I don't respond fast.
Edit: Also, I guess weight also of such a battery, but I suppose maybe the weight can be understood by how much reserve it would need.
But it could also just be that the CAPTCHA is hard because the site cranked it up for non-US users, if you're not in the US like I am. There are many EU and Asian countries where I flat out cannot access perfectly benign websites (e.g., Home Depot†) if I'm shown on an IP from these countries.
So scan, but I doubt it will find anything.
† true, when I was in Georgia (the country) during the time that Home Depot had the huge skeleton yard decoration, I couldn't even access the Home Depot website to look as Home Depot was blocking it. The page would resolve and load, but Home Depot served up a 403 for every page. Using VPN with the US or western/northern EU countries worked, but eastern EU countries also got 403.
But my personal frustration with scenarios that I've dealt with isn't about specific groups, it's that I imagine myself in like a kids TV show and we're all having to participate while some person in the company learns the value of being honest and taking responsibility for their mistakes.
except unlike a TV show, the stuff isn't resolved in 22 minutes, it takes months, if we ever resolve it, and it creates a lot of stress, frustration, anger, and costs a lot money.
and the person(s) who caused all of this don't learn anything except how to make someone else deal with the fallout of their bad decisions :))))
The EFT here creeped in and more or less turned a team that always succeeded on the goals they were actually hired and trained to accomplish and now is being held responsible for the success/failure of so many other teams, including those that have nothing to do with any of our specialties. We lost members who went on to better things, and to this day I still am only happy for them that they were able to make that change when they did.
It's not about whether or not we _can_ accomplish the load, and that's not what the article is about. It's about others pushing their items they don't want to deal with onto others, and how much effort goes into that from the others instead of just doing their work, and how EFT is toxic once it becomes accepted for persons to engage in EFT.
While this seems like we'd be a fairly carefully protected resource, over time, just everything started being thrown at us, including stuff that had absolutely nothing to do with our team. It's a big international company with different managers on other teams coming and going, so it's never clear who in the company knows about our team yet.
- early on, it was just a few people making requests directly to me, and a small portion of my day was turning down these requests
- as time went on, the team grew, we succeeded more, and more and more irrelevant requests started coming. We turned them down, but the amount of requests and the irrelevance and importance of the requests were all increasing, the latter two often linked very closely together
- at some point, we started getting exceptional push-back when we turned down requests. the first few times were rough; manageable, but I had to dedicate a few meetings/days to getting rid of this request and the requestors were very upset when I turned them down
- eventually it got to the point where a good 40-50% of my week was dealing with irrelevant requests and increasingly aggressive resistance when I turned it down
- the requestors around this time began just trying to circumvent me; find the people on the team I was leading who were not as good at saying "no", and getting the tasks in that way. I had to eventually put a full stop on requests that didn't come via a specific channel; this in turn resulted in a lot of drama from other teams complaining we were being prima donnas, and arguing with higher management if we should have the _right_ to insist on requests coming via a specific channel (something basically every team does...), which eats up more of my time as I'm having to explain to execs that have absolutely no idea about this aspect of the company, but believe the requestors when they say "yes, this team must solve this", keeping in mind that the task has absolutely nothing to do with our team, they just want us to deal with it
- a corollary to the above point, keep in mind the requests are still coming in while this debate is happening since the debate is whether or not we can restrict the channels for making requests, so my teammates are still being harassed every day by these requestors
- finally we get "approved" for the right to a dedicated single channel for the requests, and the requestors just ignore it anyways; there is no reprimand for the persons not following the approved process, and the entire debate was a pointless exercise
- I'm spending 80% of my time now arguing with these requestors and telling why we're rejecting their requests. Most of these requestors are repeat visitors, so it's not like they don't know these reasons and rules, they just don't care, they don't want to deal with the shitty task they made
- eventually, the requestors realize they don't need to request it to me, they just need to request it to an exec who has _some_ oversight over our department, give those execs enough worry to convince them we need the best, and the requests are routed to my teams. so I end up accommodating and adding meetings with these execs on the regular in hopes that they at least ask me if this really needs my team or not (spoiler: most never ask, they just lay down their decree and expect it to be done). My week is now about 95% just telling people to knock this shit off, but the tasks keep coming
- my team is burnt out, we're absolutely fed up with all the work, and even worse, we're having troubles sorting when we really do need to be on a task as there are just so many, so actual projects we _should and could have helped with_ are now in trouble as they got deprioritized. these are indeed important projects that need us, and by the time we get to them, they're in such bad shape due to mismanagement and awful decisions that it's a ton of work to get the project off life-support, and that is typically as far as we can take it before we have to shift the focus to another dying project
There's a lot here, but remember, my team is filled with IT specialists and we're supposed to be helping on specific difficult projects that align with our specialties and nothing more. Yet now more than 90% of my job is just solving arguments or problems that other teams created, doing work that has 0 to do with our team's original focus, struggling to keep the projects that are our focus just barely treading water, and constantly having to explain to extremely aggressive and emotional people that their personal unwillingness to have tough conversations with clients or their unwillingness to fix their own mistake is their problem to solve, not ours.
I absolutely can empathize with the article as it's basically all I do at my work anymore, and it's really awful to wake up and wonder "who's bullshit am I going to have to deal with today?" when I should just be setting up a few environments and writing a bit of code while mentoring the team I'm a part of. The fact that everyone participating in this EFT has been told in no ambiguous terms many times why their requests are bad and not for our team, but I guess the company decided at some point we're just going to waste everyone's time arguing on such things instead of doing IT work at some point.
Guess I missed that meeting in favor of explaining to some exec why the project their team proposed is basically giving away thousands of work hours for free just because some sales team didn't have the courage to tell a small and awful client "nah we aren't doing that"
I do tell the team just to ignore those requests and report them to me, yet the people making the bad requests just get more aggressive with their requests, either exaggerating the importance, exaggerating the requestor's "right" to assign the task to my team, etc.
The end result is that we end up closing the means to talk to my team or I am brought in more often to deny the requests, which means I'm spending more time explaining why we aren't doing stupid and wasteful things like giving some sales teams' client free work for a year (can easily cost 6 or 7 figures USD) without getting proper approvals from all the teams required to provide that work. Examples _like_ this happen way too often and it can be weeks worth of emotional meetings explaining why the original requestor needs to deal with the mess they made themselves.
My team is a bunch of IT professionals, and they should be doing IT work, not spending weeks convincing other teams to clean up the messes they made or preventing months of commitments for projects that should never have been approved, and it does _NOT_ feel good or right at all to make them constantly do something that is objectively not their job, and the end result is I end up burning out badly intercepting all of these requests.
The article was very relatable for me and EFT is a term I am going to be using moving forward.
I still see huge groups drinking and smoking outside every night at the pubs near where I live, but I can't say I've ever needed to complain about their noise levels, so people definitely seem on board with it; I can't say I've ever seen/heard persons getting into a heated discussion over noise, but naturally this is just my limited point of view and reality may differ.
Edit: also, just remembered that I even saw a more active approach to this when I lived in Saint Petersburg, Russia, where a few bars even had a "noise meter" outside the bar (just a simple dim but legible LED screen with the purported noise level and a sign explaining that if the number is > N, you're being too loud). It seemed to work pretty well.
I would take the opposite approach and figure out how to maximize the return on the white noise without changing anything for the users; that is, focus on reducing the cost to deliver white noise, work on guidelines for the white noise presenters on how you're going to monetize this without disrupting the fad, etc.
From my perspective, I just can't see how trying to do something special with this fad does anything but immediately kill the fad. There are even FOSS white noise apps, and it won't take long for users to find a free alternative if Spotify messes with the recipe here. I sincerely doubt anyone is going to get Spotify exclusively for the white noise nor that white noise will somehow be a gateway into further Spotify use; I just don't see that the persons who want white noise would use that as an entry point into the service, it's the other way around, with current satisfied users finding out they can also use Spotify to get white noise.
Basically I see this as a happy accident for Spotify that will break if they try to press on it too much. They should treat this like a beneficial fad, and just figure out how to deliver it with the least resource cost, and just enjoy the extra revenue. I don't think it's really going to draw people in except if they play the "yeah, this is legit, we're just gonna get out of your way as much as possible here. enjoy our ads", and ride that money until it dries up.
From my own experience teaching newbies about bash, the only hard part about all the flags was getting newbies comfortable with ignoring them at first and just trusting that `ls` lists files in the current directory, `sed` let's you manipulate text in a smart way, `grep` finds things, and so on. Once they got that in their head and understood that the flags just allow very specific operations that you previously needed to write a lot more code for, most people got it pretty fast and could punch out quick shell scripts to help with their work. But the base commands without a slew of flags was still quite useful for these newbies.
Again though, that's just my experience and it was fairly narrow in scope for accomplishing specific troubleshooting tasks, so that may factor into why I saw success here; I don't know if the people I taught further evolved their scripting skills past basic troubleshooting, though I am fairly confident these persons understand the "kitchen tools" nature of the GNU core utils as many ended up writing scripts on their own for situations we never discussed, and the scripts were pretty okay.
Edit: Typo, changed Exceptions to Extensions in the first paragraph
and we've done such a good job of training users to detect suspicious behavior, and here we are using the same suspicious behavior that spam sites use, it leaves me with a frustrated feeling.
Probably you start at a page like:
sso.company.com
When you try to access a service, you're taken to probably something like
sso.company.com/auth
If your company uses Microsoft or Gmail, very likely before you reach your SSO login, it may temporarily flash MS/Google's auth page briefly before redirecting or loading the elements for your company's SSO portal
After login, probably it will then load something like:
saml_provider.company.com/autheticate/redirect
saml_provider.company.com/[some generated string in the url]/some_action_page
and depending on how it's configured, you might go through a few of those types of URLs with no direct connection to your company or the resource you want, but it's just the authentication process passing your authentication from service to service until finally it figures out to return you to your originally requested resource and it passes an auth token. †
The reason I think this is frustrating is that it's very fast, no user input, but it is observable by the user; you will see the pages loading and the long urls, sometimes some basic info is printed to the page with simple HTML, but the user has no idea what's going on.
Combine this with the fact that this is exactly what happens when you accidentally click on a spam site from search results, and my problem is "how can a user possibly know if this redirect spiral is a legitimate authentication process or if they've accidentally clicked on something compromised?"
† sometimes these auth-spirals don't even take you to the correct item you were trying to get to in the first place, it takes you to a generic landing page...Reddit is guilty of this from my experience where logging in to subreddits that are flagged NSFW will redirect me to the reddit front page instead of back to the subreddit I initiated the log in to check
I think this is definitely where the security trends in modern IT have gone very awry, as it _is_ extremely annoying to be an end user having to work with modern IT security practices. Off the top of my head:
- MFA everywhere means that if you have any issues with your alternative authentication devices, you are completely locked out of your work and probably your life until you get that resolved
- broad and vague block geo-based block lists means users just flat out cannot access resources depending on where they happen to be, which means service desk tickets, investigations, and ultimately people who cannot access non-sensitive data they should be able to just because of where they are physically located
- CAPTCHAs can lock entire classes of persons out of specific services as the CAPTCHAs aren't easy for these classes to perform on demand
- SSO/SAML authentication pages take you on a whirlwind tour of dozens of randomly generated authentication pages meant to establish and pass your authentication back to a central location, and it makes it impossible to tell from the URLs themselves whether or not it's suspicious or not unless you know the specifics of the system in use; this is particularly bad because this is exactly what it will look like if you click on a spam site in a search result or a compromised webpage. how is a user supposed to know when they've accidentally gotten tricked into a compromised authentication page? the uniquity of SSO for logins is nice, but it also means that as a user, I expect that I can be taken to an SSO from just about anything, so how am I supposed to know if the entry point from page X is legit compared to the entry point from page Y?
- a corollary to requiring multiple authentications even from the same device (looking at you Microsoft...) is it creates uncertainty as to when I should expect to have to sign in; if opening a link to a report requires me to authenticate or just accessing an internal web portal requires additional auth, why should I be suspicious when my colleague's account gets compromised and an attacker sends me a link saying "hey, we need to respond on this form by EOD; don't have time to explain in full, but it's pretty straight-forward. I'll follow up in a few hours when I'm done with another item"
- Edited: another corollary with SSO means that getting auth'd once means you get auth'd a lot. While you should need to configure additional security and checks on more sensitive services, since you're already auth'd through the main means of identification, it's often trivial to get the access by normal means or to social engineer access
It really sucks to be an end user in such environments, and it's just too easy for IT security to absolutely lock out legitimate users who are following the policies as best they can with earnest intent.
> I've also seen a lot of people give up on arguing with those non-technical people about scope and time, say "OK"
I understand why this happens, and it is extremely frustrating; consequently, this is why I really dislike the trend of complaining on social media about issues because at least with my company, this is an almost guaranteed way to ensure that a C-Level will "step in to correct this", which in fact just means that now the company needs to do what the C-Level said so the C-Level doesn't look stupid in public, even if the thing to do is absolutely disastrous.
The best advice I can give if you're in a technical leadership position and you know this kind of thing happens in your org is:
1. Figure out who these non-technical persons with the ability to make said bad calls actually are in your company; do a process review on the last few events that triggered poor decision processes and find out from whom those decisions actually came from
2. Understand how that person processes information, how they're getting alerted, and most importantly, just get to understand them and what makes them "tick." (e.g., one of our lead PMs, usually a very good PM, unfortunately has a huge ego. Arguing with them in any public fashion causes them to get very defensive out of fear of looking "stupid"; a quick chat with them in private usually is enough to convince them of their mistake, and then we get more reasonable reactions)
3. Become professionally friendly with the common reporters of the issues that usually prompt bad decisions; if a particular sales team is finding actual issues but representing them in a way that results in rushed/poor decisions, teach them another place to report the issues so that more necessary stakeholders are able to view the issue before it gets to the decision process
4. Develop strong and strict change management processes that will protect from the issues; don't attach these processes to specific incidents, but instead present it neutrally as a best practice in change management, and then use the process to protect against such rash changes. The first few times upholding the process might be rough, but just remind people why the process exists, that the goal isn't to stop all decisions, but instead to ensure you are properly vetting decisions on core elements
Implementing this is difficult, especially in orgs with poor discipline and process control already, but from experience with such orgs, most persons will pay lip-service to the initial neutral presentation, and won't realize that the bad behaviors they have which the process is meant to stop will be impacted. The goal here isn't to be dishonest with people, but instead to introduce a process-based prevention in a palatable way which makes future discussions easier as they'll carry a common point of agreement. At least with the C-Levels I've had to deal with, it was effective because they didn't want to look stupid in front of other C-Levels and higher management who were telling the C-Level "this breaks our internal processes, we need to review this first as last time we rushed decisions without the stakeholder input, we ended up with huge costs". It doesn't stop every C-Level, but it has greatly reduced the number of meetings I've had to have where I have to give "Explain it like I'm 5" presentations to non-technical decision makers to prevent disastrous decisions/changes.
Edit/Addendum: I am well aware that the "real" solution is that decision makers just stop making drastic and ridiculous decisions/promises, but I don't think it's reasonable to expect to change personalities/poor thinking skills in a person, much less to force changes of management. Instead, I'd rather just use process to enforce this and deal with the occasional raised voices.
Also Edit: fixed numbered list formatting.
I don't find this weird or unusual at all, just different than how I've handled file management on computers since I was a child using the family computer; I did notice the way computers stored program data when I was first learning computers and while I had a vague understanding of how programs worked, the conclusion I came to as a child was "just don't mess with the stuff the OS uses and make your own folders instead."
Usually I have my personal documents in some folder(s) under / or on dedicated drives, separate from the OS/program directories entirely whenever possible, and I treat any pre-existing folder structure as "the OS' and programs' folders" and just don't use them at all (with the exception of ~/Desktop and ~/Downloads which more or less I use normally) I understood early on that developers might make their workspace just about anywhere so I don't particularly care about the system defaults and instead try to keep my data in its own location outside of any system defaults whenever possible. The before-mentioned ~/Desktop and ~/Downloads I treat just as temporary directories for me and fair-game for other processes, so my workflows specifically don't keep any personal or sensitive data in common system directories.
For a few schedule things that needed more management than just a shared calendar, I wrote a script to pull the schedule out of Outlook and convert it to an HTML schedule sheet which I can just copy/paste right into Teams with perfect formatting (I send it via a bot, but it works for users to just paste into the doc also)
I'm not a fan of powerpoint presentations in any form; I find the medium uninteresting and more of a progress meter for the current meeting than anything else, but even that hasn't been reliable for a long time to know how long a presentation will go, but I don't think using powerpoint in one of the many ways it can be used is anything bad; I'd rather that such hypothetical execs have someone put the notes into powerpoint than write it down on a paper notepad. At the end of the day, all I really care about is that I can read the notes if required and I can quickly access the data without having to bug someone after the initial permissions are set.
(all this being said, I cannot express how frustrating Microsoft Office and Google Office are to me; barring powerpoints where I have no choice but to build it in one of these office suites, I usually just write plain text with markdown formatting and only use office suites to apply the necessary formatting, using the markdown as a reference; I would enjoy word/docs a lot more if there was button to "convert markdown to word formatting", and vice versa)
If your active threat scope involves governments, don't expect them to behave with regards to the laws where you are; either they don't care and will just deal with the fallout, or they have explicit approval do to illegal or wrong things.
I don't have an answer on how to check for spooks, I guess you'd have to do reverse reconnaissance, but I have no idea how feasible it is. But testing legal and social norms is not reliable; governments are not really bound by their own rules, especially when it comes to branches dealing with security or intelligence.
But to be clear, law enforcement agents (all as far as I'm aware) are allowed to do illegal things to catch their mark. In the US at least, this is not entrapment unless they forcibly coerce you to do something you normally wouldn't; just smoking or snorting some stuff in a casual setting isn't enough, they'd have to have you more or less at gunpoint or threatening in another way to make you do it.
Just a very important fact for people to remember: Law enforcement agents in the US can and will lie frequently and do illegal things in pursuit of their goal.
Entrapment does not mean what most people think it does, so it's not good to rely on this, as entrapment has a very narrow legal definition far away from the layperson definition.
We have been trialing this with our support team for awhile and a lot of higher execs were ready to sign off and dump rather large sums on some models, but eventually we were able to convince them to delay; the bots are just too prone to convincing but wrong answers, and our buy-in from clients is way too polarized: either they uncritically believe the bot or they are overly skeptical of the bot.
the tech is very cool, but I don't think that the technology or humans are at a place yet where it's ready for full on use outside of very controlled situations. I could see it being very useful as an addition to search fields or to maybe monitor the user's search inputs/actions and based on what the user is looking up, show some context-aware prompts.
What I'd really like to see is a bot that is extremely skeptical and shows the user its skepticism in an unambiguous manner; classify the data and make an internal flag where if the bot's skepticism is above a certain threshold, it finds knowledge holders it's aware of to work through the bot's skepticism and never act on the information until the bot has lowered the skepticism value after checking.
right now my experience with the bots I've played with is that they either just shut down the conversation without advancing it or giving the user paths for research forward, or the bot confidently just pumps out any answer it makes that fits as a response for the given query, and I think we need the bots to show skepticism and explain to the user what this skepticism means. (i.e., the user should be alerted that the bot isn't confident on an answer, why the bot isn't confident, alternatives that the bot understands to be equally relevant or worth consideration.
it can still be polite, but the bots need to share when they're out of their league and work to correct it; I think people will actually appreciate it, and the bots are well suited to this position because they have no emotional stake in the game, so users can get as upset as they want that they don't have immediate disagreement, the bot won't change its position just because the user is upset.
I get probably this is a popular video maker in whatever sphere he's in, but as an outsider, it's difficult to get into the video because of what I attribute as the presenter's YouTube personality.
(also it very much so bugs me to see people using Chrome and see all the nags for notifications, the random extensions/features, etc. And any browser without uBlock origin throws me as it takes me a minute to realize why all the websites look so bad, but that's just a personal issue :) )
The sect I was a part of did not honor Saints, it instead focused on the JC boy.
Jesus' callout here was on their callout; the story of Jesus in the Bible if you subscribe to Jesus was that he was the real deal and sent to close the previous covenant between god and humans, and preach the new word of god.
in the context of the book of mark, Jesus had been busy for awhile pointing out the fallacies of the current religious authoritarians and debating classic scripture with them quite successfully. the intent of the story would more accurately be that the Pharisees were the ones doing the random ad hom callout after getting bested by Jesus during debate, and he responded with a prophesy from Isaiah that is relevant.
I mean I get your point, but you need to understand that the entirety of the Bible read through a modern lens is really just a holy version of social media drama, but with a literal deity involved. the reason Jesus' response is supposed to be so big here is because his entire point up to, during, and after this is that the old laws are not relevant because humans cannot ever atone for their sins or stop sinning, so Jesus is there to solve that, and set some new rules.
and keep in mind, this is just how _I_ was taught growing up in my sect; other christian sects don't take the same interpretation of this...in other words, don't focus too much on the specifics, it's very much so open to interpretation and the Bible has so many conflicting authors and ideologies that it self-supports so many interpretations
I'm sure there will be people who instead of just sharing their interpretation will try to prove that mine is wrong :) and I'm pretty sure we could argue for days if we wanted to, and the Bible and the history of theological study would probably produce troves of thoughts and evidence to support all the interpretations and more, and we might even start a new sect accidentally while arguing :)
I suspect you are correct because newest and greatest typically solve a problem, and that's the focus for the devs. the more senior devs I know take an "optimistic but cautious" approach, while less experienced devs/non-devs typically just see an answer to their particular problem and want to use it, as defending the use and the few broken instances is typically easier than solving the issue without the latest and greatest. and I can get that easily
admins probably like old and trusted because boring is exciting for them; for a few of the systems I admin, it's great to have a few on debian/bsd where they've proven that I don't need to babysit these systems; they're never fully out of the equation when troubleshooting, but it comes up rarely, and if worst comes to worst, a reboot on these systems is typically so fast and non-disruptive that it's an easy decision, which often helps and then the issue never returns. sure it's not good that I had to reboot, but a down time of 10 seconds while I boot and it never comes up again is appealing.
Sharepoint and Google drive really feel like they have gone out of their way to make the permissions scheme as convoluted as possible, and it's never clear for me whether I've shared it in a way that permissions can propagate from those I shared it with or not. sometimes I can further share a received Sharepoint document without issue, other times I cannot, and I don't know what the difference is. some of my shared docs that are only shared with specific users can be shared freely apparently, other times when it gets shared further I get automated emails with access requests, even though the public access list is disabled/empty on both cases.
I really wish that the user:group:world wide model was the basis for these permission schemes and it was easier to just set people/groups and the specific actions they can take on a shared file/document. I get why the companies call it sharing, but it shouldn't be thought of as sharing, it should be Grant Access. I think it gives a better mindset for what you're actually doing, and the design should be around the idea you're giving access, not sharing, which is not the same thing to me.
the article is a call to get you comfortable picking/using BSD, and from my point of view it's reasonable to advertise its maturity.
OOC, why does this stand out for you? Just to explain my curiosity, I've worked on Mac since I was a kid starting with System 6 and then going to OS X when it came out, so Apple's "your program is all in that file" just kind of made sense to me and it was really convenient to just drag a file to the trash and the app is _mostly_ gone, minus a few .plist and other config files in ~/Library.
But I _like_ the old forums and sites that still show the stuff like page_id=N; for the boards and forums I go to, it's very useful to just jump around long topics or you can play with it on your shitposting.
Plus most modern browsers truncate or hide the full URL anyways; I dislike this feature personally, but at least Safari's concise tabs are a good balance for someone like me.
>You may use the discounted license if:
> - You are an individual, and REAPER is only for your personal use, or
> - You are an individual or business using REAPER commercially, and yearly gross revenue does not exceed USD $20,000, or
> - You are an educational or non-profit organization.
Oh, it actually seems pretty reasonable. At least as someone not involved in the DAW space. $60 for professional grade tools on a non-subscription looks like it's comfortable for someone to get into this.
- if there is success in the UK, relevant persons at Apple can make a more compelling argument to push back on China and other governments a lot more
- perhaps apple is still pushing hard on china and using the UK as an example that they're willing to drop a long time strong market over the anti-encryption legislation
I'm not saying either is the case, but there are benign or even positive reads on why apple is more aggressive with the UK