Bruteforce IRL

So I recently bought my first house (yay!).

Whilst doing the initial viewings I saw the below on the backyard and thought "hey that's neat, I can leave a key in there for when I come in late and my fiancée is asleep.

Fast forward to moving in day and the previous owners hand me the keys so I ask "oh yeah, what's the code for the keysafe" and he just looks at me completely blank, so I'm just like "the box on the wall out back" and he's just like "oh! So that's what that is. No we've never had the code for that, bye."

Being a pen tester I'm just stood there dumbfounded thinking "How the hell can you have a locked box attached to your house and not want to know what is inside!"

Anyway, that brings us to now where I'm stood outside in December on a Sunday morning brute forcing my way into my own keysafe.

I wish this didn't run so many parallels with my work life 😂

I am an indie game developer and I lead a team of 5 trusted individuals. After our latest release, we bought a larger office and decided to expand our team so that we could implement more features in our games and release it in a desirable time period. So I asked everyone to look for individuals that they would like to hire for their respective departments. When the whole list was prepared, I sent out a bunch of job offers for a "training trial period". The idea was that everyone would teach the newbies in their department about how we do stuff and then after a month select those who seem to be the best. Our original team was
-Two coders
-One sound guy(because musician is too mainstream)
-Two artists
I did coding, concept art(and character drawings) and story design, So, I decided to be a "coding mentor"(?).
We planned to recruit
-Two coders
-One sound guy
-One artist (two if we encountered a great artstyle)
When the day finally arrived I decided to hide the fact that I am the founder and decided that there would be a phantom boss so that they wouldn't get stressed or try flattery.
So out of 7, 5 people people came for the "coding trial session". There were 3 guys and 2 girls. My teammate and I started by giving them a brief introduction to the working of our engine and then gave them a few exercises to help them understand it better. Fast forward a few days, and we were teaching them about how we implement multiple languages in our games using Excel. The original text in English is written in the first column and we then send it to translators so that they can easily compare and translate the content side by side such that a column is reserved for each language. We then break it down and convert the whole thing into an engine friendly CSV kind of format. When we concluded, we asked them if they had any questions. So there was this smartass, who could not get over the fact that we were using Excel. The conversation went like this:(almost word to word)

Smartass: "Why would you even use that primitive software? How stupid is that? Why don't you get some skills before teaching us about your shit logic?"
Me:*triggered* "Oh yeah? Well that's how we do stuff here. If you don't like it, you can simply leave."
Smartass: "You don't know who I am, do you? I am friends with the boss of this company. If I wanted I could have all of you fired at whim."
Me:"Oh, is that right?"
Smartass:"Damn right it is. Now that you know who I am, you better treat me with some respect."
Me: "What if I told you that I am not just a coder?"
Smartass:"Considering your lack of skills, I assume that you are also a janitor? What was he thinking? Hiring people like you, he must have been desperate."
Me:"What if I told you that I am the boss?"
Smartass:"Hah! You wish you were."*looks towards my teammate while pointing a thumb at me* "Calling himself the boss, who does he think he is?"
Teammate:*looks away*.
Smartass:*glances back and forth between me and my teammate while looking confused* *realizes* *starts sweating profusely* *looks at me with horror*
Me:"Ha ha ha hah, get out"
Smartass:*stands dumbfounded*
Me:"I said, get out"
Smartass:*gathers his stuff and leaves the room*
Me: "Alright, any questions?"*Smiling angrily*
Newcomers: *shake heads furiously*
Me:"Good"

For the rest of the day nobody tried to bother me. I decided to stop posing as an employee and teaching the newcomers so that I could secretly observe all sessions that took place from now on for events like these. That guy never came back. The good news however, is that the art and music training was going pretty well.

What really intrigues me though is that why do I keep getting caught with these annoying people? It's like I am working in customer support or something.

Developed an android app for the client. It was going great. Prototype for the initial (and static) content to show to the client was on the way. All until...

*goes back in time to when we were developing the prototype*

The asshole boss: "Wow this is good, just remove the login after the splash screen. Redirect it to the dashboard immediately."

Me: "What? Why?"

TAB: "He (the CEO of our company) said that the client doesn't need to see the login."

Me: "Well, alright." (Orders are orders, better remove it)

*A few days later, we present the prototype to the CEO. He'll be the one talking to the client. TAB isn't in this meeting.*

CEO: "Where is the login screen?"

Me: *dumbfounded and confused, in silence, and pressure rising*

The Good Boss: *whispers* "Where is the login screen? I thought I told you guys it should be there."

Me: *whispers* "TAB told us to remove it."

TGB: *Looks toward CEO* "TAB told us to remove it."

CEO: "Ugh. TAB is sick."

A little giggle. Nonetheless the meeting continued. He was displeased. I was a little guilty. The login screen's code was already there. Just couldn't show it since the app doesn't redirect there anymore.

*A discussion after the meeting*

TGB: "Why'd you guys remove the login?"

Me: "You and TAB had a meeting with the CEO the other day. After the discussion TAB went to us and told us to change it."

TGB: "But the CEO said no such thing! Anyway, let's go back to the office and straighten this out tomorrow."

*The next day, TAB was in the office*

TGB: *Chatting on messenger with me* "He is completely denying it."

Me: "WHAT?"

TGB: "He said he never told you guys anything. And he is persistent. I kept telling him it was his fault, but he denies all of it. He never approached you guys to change anything."

Me: "Well yeah. I guess we magically thought to ourselves and said, 'Hey, let's remove the login screen for fun. Let's show them less content because that's how we please our clients!' -_-"

Seriously, what kind of assholefuckery is this. This shit is a whole new level. I am so TRIGGERED.

I don't really care that the meeting didn't go as planned. Just MAN UP AND ADMIT YOUR MISTAKE YOU FILTHY SON OF A GOOSE. Never listening to this asshole again. Thought he could be trusted. I will always ask my good boss next time.

Alright so here goes, I currently work at a promising startup. Absolutely love it; nice, hard-working colleagues but there's only a couple of us so we all have to wear a multitude of hats.

I don't mind being on support duty or helping out a customer with a technical question but one thing that really gets to me is lazy people.

We have some instructional videos (made in-house by yours truly) around certain functionality in our app which can't be simplified any further and they're condensed to about 50 seconds each.

I receive an email from a customer saying that he wants the instructions in screenshot form instead of watching the video because he 'detests' watching videos.

I must admit, I was a little hurt because he dismissed my videos so easily without even watching them. Just because he really doesn't like to watch videos? I was dumbfounded.

Me putting (most of) my rustled jimmies aside, I take about an hour to screenshot and document each step of the instructions and send them to the customer with a note: Be careful, if you scroll too fast it turns into a video.

I receive a response saying he doesn't like to watch videos because he is deaf but he did admit he had a chuckle.

Morale of the story lads, keep the sass in in your IDE's and out of your customer interactions.

True story.

Backend internship interview

They: Can you reverse the given string without using pointers? (C++)
Me: Yeah, sure
*Then I start explaining how I am gonna approach the problem and such*
They: Ok, we understand that you can do it, now can you write a front-end that has a couple of routes. Also, these routes should have some sort of list views because we want you to print information **attention** that you are going to parse from Amazon inside those list views.

Me: *dumbfounded and trying to explain that am not a front-end developer*
They: But we still want you to do this.

Most satisfying bug I've fixed?

Fixed a n+1 issue with a web service retrieving price information. I initially wrote the service, but it was taken over by a couple of 'world class' monday-morning-quarterbacks.
The "Worst code I've ever seen" ... "I can't believe this crap compiles" types that never met anyone else's code that was any good.

After a few months (yes months) and heavy refactoring, the service still returned price information for a product. Pass the service a list of product numbers, service returns the price, availability, etc, that was it.

After a very proud and boisterous deployment, over the next couple of days the service seemed to get slower and slower. DBAs started to complain that the service was causing unusually high wait times, locks, and CPU spikes causing problems for other applications. The usual finger pointing began which ended up with "If PaperTrail had written the service 'correctly' the first time, we wouldn't be in this mess."

Only mattered that I initially wrote the service and no one seemed to care about the two geniuses that took months changing the code.

The dev manager was able to justify a complete re-write of the service using 'proper development methodologies' including budgeting devs, DBAs, server resources, etc..etc. with a projected year+ completion date.

My 'BS Meter' goes off, so I open up the code, maybe 5 minutes...tada...found it. The corresponding stored procedure accepts a list of product numbers and a price type (1=Retail, 2=Dealer, and so on). If you pass 0, the stored procedure returns all the prices.
Code basically looked like this..

public List<Prices> GetPrices(List<Product> products, int priceTypeId)
{
foreach (var item in products)
{
List<int> productIdsParameter = new List<int>();
productIdsParameter.Add(item.ProductID);
List<Price> prices = dataProvider.GetPrices(productIdsParameter, 0);
foreach (var price in prices)
{
if (price.PriceTypeID == priceTypeId)
{
prices = dataProvider.GetPrices(productIdsParameter, price.PriceTypeID);
return prices;
}
* Omitting the other 'WTF?' code to handle the zero price type
}
}
}

I removed the double stored procedure call, updated the method signature to only accept the list of product numbers (which it was before the 'major refactor'), deployed the service to dev (the issue was reproducible in our dev environment) and had the DBA monitor.

The two devs and the manager are grumbling and mocking the changes (they never looked, they assumed I wrote some threading monstrosity) then the DBA walks up..

DBA: "We're good. You hit the database pretty hard and the CPU never moved. Execution plans, locks, all good to go."
<dba starts to walk away>
DevMgr: "No fucking way! Putting that code in a thread wouldn't have fix it"
Me: "Um, I didn't use threads"
Dev1: "You had to. There was no way you made that code run faster without threads"
Dev2: "It runs fine in dev, but there is no way that level of threading will work in production with thousands of requests. I've got unit tests that prove our design is perfect."
Me: "I looked at what the code was doing and removed what it shouldn't be doing. That's it."
DBA: "If the database is happy with the changes, I'm happy. Good job. Get that service deployed tomorrow and lets move on"
Me: "You'll remove the recommendation for a complete re-write of the service?"
DevMgr: "Hell no! The re-write moves forward. This, whatever you did, changes nothing."
DBA: "Hell yes it does!! I've got too much on my plate already to play babysitter with you assholes. I'm done and no one on my team will waste any more time on this. Am I clear?"

Seeing the dev manager face turn red and the other two devs look completely dumbfounded was the most satisfying bug I've fixed.

I was on vacation when my employer’s new fiscal year started. My manager let me take vacation because it’s not like anything critical was going to happen. Well, joke was on us because we didn’t foresee the stupidity of others…

I had to update a few product codes in the website’s web config and deploy those changes. I was only going to be logged in for 30 minutes to complete that.

I get messaged by one of our database admins. He was doing testing and was unable to complete a payment on the website. That was strange. There was a change pushed by our offsite dev agency, but that was all frontend changes (just updating text) and wouldn’t affect payments.

We don’t want to enlist the dev agency for debugging work, especially when it’s not likely that it’s a code issue. But I was on vacation and I couldn’t stay online past the time I had budgeted for. So my employer enlists the dev agency for help. It’s going to be costly because the agency is in Lithuania, it was past their business hours, and it was emergency support.

Dev agency looks at error logs. There are Apple Pay errors, but that doesn’t explain why non Apple Pay transactions aren’t going through. They roll back my deployment and theirs, but no change. They tell my employer to contact our payment processor.

My manager and the Product Manager contact Payroll, who is the stakeholder for our payment gateways. Payroll contacts our payment gateway and finds out a service called Decision Manager was recently configured for our account. Decision Manager was declining all payments. Payroll was not the person who had Decision Manager installed and our account using this service was news to her.

Payroll works with our payment processor to get payments working again. The damage is pretty severe. Online payments were down for at least 12 hours. Our call center had logged reports from customers the night before.

At our post mortem, we had to find out who ok’d Decision Manager without telling anyone. Luckily, it was quick work. The first stakeholder up was for the Fundraising Dept. She said it wasn’t her or anyone on her team. Our VP of Analytics broke it to her that our payment processor gave us the name of the person who ok’d Decision Manager and it was someone on the Fundraising team. Fundraising then starts backtracking and says that oh yes she knew about it but transactions were still working after the Decision Manager had been configured. WTAF.

Everyone is dumbfounded by this. How could you make a big change to our payment processor and not tell anyone? How did our payment processor allow you to make this change when you’re not the account admin (you’re just a user)?

Our company head had to give an awkward speech about communication and how it’s important. The web team can’t figure out issues if you don’t tell us what you did. The company head was pissed because it was a shitty way to start off the new fiscal year. Our bill for the dev agency must have been over $1000 for debugging work that wasn’t helpful.

Amazingly, no one was fired.

I fucking hate all these JavaScript frameworks. You try to learn one and then there is another one that's rising up. While you wonder why a framework exists and what's the best use case there is a fresh off college grad who built a fucking app on it. How the fuck is it even possible? Did you study the framework? Did you understand how it works? Or did you just put together a bunch of tutorials and built the app. I feel people just want to churn apps out without bothering about understanding the framework. Ask them about design patterns... They know nothing about it. Ask them vanilla JavaScript questions.... They fumble easily. Ask them OOPs..... They look dumbfounded. WTF!!!

Or maybe I am just getting old. It's possible.

I remember a few months ago at my school we all had taken the Chromebooks (our county's OS of choice) out and put them on our desks. We were in science, and we needed to take screenshots of websites for some reason. "Everyone go to the chrome store," our teacher said, with a look-how-smart-i-am kind of look on her face, "search for the 'Awesome Screenshot Extension.'" Ugh. This was dumb. I reluctantly searched it up and upon bringing up the description and about to press the "Add to Chrome" button, when I stopped, and made a decision I would later regret. Now, I don't really like this teacher, and she thought she was so fucking smart for finding this shit extension. I raised my hand, and she walked over. "Uhh… I'm pretty sure you can just do Ctrl + shift + []|| to take a screenshot" I said. She was fucking dumbfounded. She yelled out "Class, listen up! [Let's call me 'Ben' for this story] Ben just found an alternative [she was trying to make her extension not seem entirely useless, even though she knew it was] way to take a screenshot. Just press Ctrl + shift plus that box with the two lines next to it. You can use my extension or the one Ben found. Whichever is easier [she damn well knew which was easier]." Three times in the span of the next five minutes she said "just a reminder… you can use Ben's way if you want" to the whole class. Everyone kept looking at me. A few minutes later, she called me up to the computer which was being displayed on the big screen in front of class. She said some people were having trouble, so then pulled all the attention on me to come up to the front of class and demonstrate a goddamn keyboard shortcut. She was running windows 8, and I knew it wouldn't work on her computer. I pressed a few random keys on the keyboard and said "uhh, I think it only works on their computers" she let me sit back down. She couldn't handle the concept that different computers run different operating systems. I sat down and the guy sitting next to me raised his hand. He said "you could use the 'snippet tool'" Yes. Some people can. But she can't. I stopped him from doing anymore damage on their small brains by saying "uhh, it won't work on the Chromebooks, so that won't help." I hate that teacher. At lunch my friend came over to me. He has the same science teacher as me. "You know what she's been saying all day?" I was confused. "What?" I said. He almost started to laugh. "All day she's [the teacher] has been telling everyone that you found this amazing new technology in the Chromebooks. [Most of the students were smart enough to know that I didnt] she was like 'Ben, from my 2nd period found this amazing thing'" End of story. And guess what? I still hate her.

I grew up with a hacker for a brother, always tampering with shit and my dad was always taking computers apart and repairing them. Although I was too little to be of any help, I was dumbfounded and couldn’t get enough. To be cool, I took all my toys apart to see what made them work. My brother taught me the dark side of a computer and my father the light side. I could go on and on, but meh.

Biggest hurdle I have overcome is <b>myself</b>.

All my expectations, worries, fears, and doubts definitely caused major hurdles I had to crash through, trip and fall into, or they downright exploded into balls of fire as I would stand dumbfounded and burned by flames of regret.

Learning I was the blocker to greater achievement, success and ultimately happiness was a very hard lesson for me to learn, and a lesson and discipline that I still battle with today.

It is difficult to climb the seven story mountain of madness with heavy burdens, plodding with little progress.

Free the weight, and the natural warm air currents will lift high the spirit, and the body will follow.

"Angels fly because they take themselves lightly" ~GKC

This literally dumbfounded me on the first day of going back to the frontend

This is long rant/story:

My manager conducts sync-up meetings regularly. The idea is to sync up all developers on current state of work. He does’t conduct stand-ups. He doesn't have time for it. He rather discusses on individual basis if we are blocked. The rule of the sync-up meeting is NOT to discuss any blockers or problems but simply explain each other what we are doing and how we plan next.

Sometime ago, the manager brought up and explained a new way of working in the sync-up meeting. At this point, a new developer in the team was absent due to sickness.

Today, there was a sync-up meeting and the manager started to question the new member about the newly introduced way of working. He was unaware of it and the manager never communicated this important information via email or any mode of communication available.

So, the conversation goes on as follows:

"Manager": — "Why didn’t you complete your task as per the new way of working?"
"Employee": — "Well, I've no idea. Am I supposed to do? I’ve been working as usual like any other"

"Manager": — "We have a new process and you have failed to follow it, so we’re late in delivering your work"
"Employee": — "I’ve already finished my work on time. I've raised a pull-request this morning"

"Manager": — "It doesn’t matter, it is not merged to main branch and so we can’t include your work in the release"
"Employee": — "I’ve no idea about the new process"

"Manager": — "Haven’t you asked around about what happened from previous meeting"
"Employee": — "Yes, I have. I was told which tasks were handled, but nothing about a new process"

"Manager": — "Aren’t you interested to learn it?"
"Employee": — "Why won’t I be interested? I was on a sick leave and I have no clue what happened here"

"Manager": — "What’s happened is past now, let’s not focus on it"
"Employee": — <Dumbfounded>
The Employee felt ashamed in front of everyone. He did his job but it didn’t pay off.

…. After an hour … the Employee had a talk with the Manager

"Employee": — "You shouldn’t have pointed me out in front of everyone. It made me feel real bad. You should have emailed this information if its important for the team."
"Manager": — "I have no idea what you’re talking about. When did I say so? I think you’ve a bright future in the team. You should be focusing on doing better things."

Employee goes back to work. A minute later, the Manager sends a PowerPoint screenshot of the process in the group chat.

**The Process**
It's about delivering release packages based on priorities defined by client. Each release package is a set of work items or requirements. Individual developers are assigned to work items. They are expected to deliver on planned delivery timelines in order to consider a work item into a release package.

!rant

Met up with a good friend today we go off roaring all the time since we both own hooked up Jeep wranglers. Well we got together and after a fun day of crawling (no coding 😞) lol, We went to eat and I pulled up devRant and kind of mentioned how much I loved this little app and stuff and why it was about. Well turns out that I’ve been friends with this guy for sometime and we never talked profession. This guy is the Vice President to a large scale software development company here in my state!

I was dumbfounded ! Lol all this time this dude has been in the same field and I had no clue.

(I don’t get out much) 😅

I'm working with a consultant group at my company to implement a new authentication strategy for our entire platform.

The senior dev lead from the consultant group has 25+ years consulting and claims to have written a web browser for the blind and all sorts of in-depth accessibility things.

Stakeholders tell us "Don't forget about accessibility compliance on this project"

Senior dev lead with all this claimed accessibility experience asks me, "What does accessibility mean?"

wasn't a fight, really, just me having gotten frustrated after half an hour of trying to explain to a 2D animator what smear frames are, since we were making a flying hummingbird, found out that multiframe animations for the wingflaps looked like crap for its flapping speed, so i was like "oh, i know, let's just make the whole wing flap a 3frame anim, one frame wings down, one smear frame, one frame wings up, done"

cue the UNIVERSITY EDUCATED ANIMATOR looking at me with confusion, asking what are smear frames.

cue half an hour of repeated attempts at explanation, each attempt imagining him to be a younger and younger child, last 3 attempts i was actually sketching it out for him in photoshop and playing it to him (via photoshop's timeline for making animated gifs) so that he could see how it looks, which still didn't help him get it.

it turned very unpleasant towards the end, due to me getting very dumbfounded and irritated and interlacing the last couple of explanation attempts with remarks on my fascinated disbelief that a university educated and graduated animator not only had no idea what smear frames are, but isn't even getting it after having it explained multiple times as if he was an elementary school child.

at that point my boss stepped in, told me to go have a smoke, and when i came back, he managed to explain it to the animator by some of the interpersonal magic he (the boss) had.

that dude (the boss) was amazing.

p. s. the hummingbird turned out looking amazing, thanks to the smear frames.

-4 Domain Administrators in my organization-

Me, a Doman Administrator: "Boy, I sure hope the FDIC IT Audit goes well!"

Braindead FDIC Examiner: "So let me get this straight, you use your administrator account to do things on a day-to-day basis?"

Me: "Uhh, I'm an admin so yeah, my account has admin privileges."

Examiner: *gives disapproving glare* "And your personal account has administrative rights?"

Me: "...I'm an admin... So I thought that'd be fairly obvious."

Examiner: "I'm sorry, but that is unacceptable. How can we tell which admin made what change when?"

Me: *dumbfounded* "...I'm sorry, what?"

Examiner: "You're going to need separate accounts, 1 normal user account and 1 admin account per domain admin."

Me: "You do realize that everything I do while I'm working requires elevation of SOME kind, don't you?"

Examiner: "I'm sorry, but you need to make this change. Thank you."

Me: *stares at the short pile of braindead shit as he walks away*

Doing pair programming while I was navigating on somebody else's computer, we hit a weird behavior that our code changes weren't reflected.

Trying everything it turned out: I forgot to save.

Yet: Why though would you make me save? And why did the IDE not warn me about compiling unsaved changes? I think it was eclipse for Java, oh well. What can I expect ...

Anyways, I have gotten so used to my editors autosaving content for me as I write it, that I completely forget about doing Ctrl + S myself.

I never understood the need to hit that key combination manually as if I break something: `get reset --hard` will help to get me to a working state. (And even if I mess it up differently, my IDE's local history also let me restore recent changes.) And if it is a workign state, then I like to commit early and often. and

I am really dumbfounded why people insist on hitting save themselves.

Got a new devops "manger" today we had an argument for 20 mins about why Staging/UAT was needed and why we could not just by pass it and get to prod quicker .. WHAT?! I am dumbfounded I do not have words to express the emotions I am having right now.

So, today, I wanted to try setting up a wireguard VPN server on my little raspberry pi at home. I... expected /some/ issues, but what I found dumbfounded me.

1 - I already had the wireguard package from the unstable branch of the main raspbian repo installed... Huh, okay.
2 - Setting up config was extremely easy... Wow, so the rumors were true. Wireguard really is almost dumb-simple.
3 - Failed to create a network interface? Oh, trouble, here it is! So lets see... modprobe wireguard... Nope. Don't have the module? What?
4 - Reconfigure package to rebuild the module - missing kernel headers? Huh... weird

This was the simple stuff... Then I went down the rabbit hole of the Raspberry Pi ecosystem:

1 - There is the Raspberry Pi Bootloader, that is apparently separate from the Kernel itself. And I didn't seem to have any of the standard linux-image-* installed... What? Weird, yet there I was, running a 4.19.42-v7+ kernel...
2 - No kernel and no headers... What... The... Fuck
3 - Okay, so... Lets just... try to install the latest kernel image then? One apt-get install... It downloaded the image, but during package configuration, it failed because... I didn't have... its headers? What? What for? And if it needs them (for whatever reason), why isn't the headers package as a dependency? Ugh, whatever...
4 - Another apt-get install and... Okay, building the initrd image aaaaand...
FAIL
WHAT. What is it this time!?

Oh... Ran... No more space on device? What? Is /boot independent? Of course it is, it has to be, its a bloody different filesystem

Okay, so, lets che-OH MY GOD WTF.

Its just bloody 45 MBs big! The entire /boot is just 45 MBs large. WHY. THE. FUCK.

This was a default raspbian install from I have no idea when. But... Why. Oh WHY would ANYONE pre-configure /boot to be this incredibly tiny!?

No wonder the new init ramdisk couldn't fit in there! Its already used up from 64%!

Thanks, Raspbian Devs, now I gotta reinstall the whole system because, yes, the /boot is, of course, sector 8192. Just far enough from 2048 that there are *some* sectors free - About 3 MBs.

So what did I try? Remove the partition and recreate it from the very beginning. Only... I never tried in in the past, and okay, kernel doesn't like having the partition where its image resides deleted on the fly, it will not give up FDs pointing there or something.

So now, I have a system I cannot reboot, or it will never boot back up :|

Thanks, Raspbian!

I need to get a cheap 1U somewhere or something T.T

The only advice I ever got about transitioning from a dev student to actually working in the dev world came when I was on my first semester in an elevator from a random person who already had a job in dev. Not her words, but paraphrased later by someone else:

"The only qualification you really need to make it just fine is the ability to utilise search engines better than the average gorilla"

... and she was right. Also, never before had I noticed, and I was dumbfounded when I did, how bad people actually were at searching for information.