Press J to jump to the feed. Press question mark to learn the rest of the keyboard shortcuts
Coming soon
33 points · 19 days ago

You have a ton of options to spice up your taverns, I am not 100% sure where you feel yours may be lacking but here's a couple suggestions.

Create cards or cliff notes beforehand to give a short paragraph description of what the tavern looks like, specify if it looks clean, grungy, old etc. This can be either flavor text or it can be a way to reveal a clue for something else.

If you and your crew like minigames or puzzles, add some to the tavern. A locked box, a Simon says game with a troll, a word puzzle with a philosophical Elf. Or a game of dice with some local thugs.

A final misconception that can happen is what I feel may have come from videogames, savepoints. People feel in a tavern or town the story has stopped and it's safe, henchmen need a break too! They can run into enemies in a city just as well in an underground catacomb or wizard tower.

I hope some of these help, I can elaborate more if you have questions!

The Don (my goldfish) wedges himself in to corners of his tank and sleeps, still freaks me out as well!


Greetings everyone!

Haven't done one of these for a bit so lets do one! I've been working on multiple writing projects of late, unfortunately many of which were either not completed or not to my satisfaction, so that's why I haven't posted yet!

I have several exiting projects coming to completion that I want to share now, but my u/Zirq advised I wait until I am more done! Real life has been exciting, the sister-in law has purchased a home and needed some help getting projects done so she can move in, so we've also been busy with that.

I guess I am rambling a little, so I will go ahead and put in some common PM's I've been getting lately!

Q: Will we ever know what happened to Sup1?!

A: Stay tuned in to find out!

Q: How do you remember everything in such detail?

A: I think I've said it before, but I have piles of notebooks that I have kept ever since a specific work incident. I partially used them as personal journals as well, recording external factors which range from major life events down to what Snickers wanted to get for lunch. (A terrible drawing of taco's on the borders of the pages are good indicators.)

Q: When is the next IT Newbie book coming?!

A: Life has been busy, but we are working on it! It takes lots of time to get editing and formatting done, but I suspect sooner than the next Game of Thrones novel!


Is there a story as to the specific work incident that caused you to document everything in the notebooks? Have you already written said story and I am just ignorant?

Excited for more stories!

see more
Original Poster3 points · 20 days ago

That would be around IT Newbie does some training

3 points · 22 days ago

I have a plethora of journals and notes. Early on I would use many similar methods, numbering pages making it easier to reference a previous occurrence of something (often I used these for work related issues) so I could see my process to resolve an issue in the past and what caused additional complications along the way to hopefully prevent a reoccurrence.

I had kept journals prior to work, but after one particular incident I started really documenting more heavily, and leaving space for indexes and using key symbols to more easily find a particular type of event.

A small LPT from me would add to feel free to include life events in your work journals (assuming it's not too private or a publicly shared document) this can help you find things faster and keep your previous state of thoughts in context. Allows you to look back and see where your head was so you can gain insight into your own head.

3 points · 1 month ago

A plate of fish... They had been in the middle of lunch, and were called into a meeting (during which they were terminated)... A few hot days go bye with their office door was closed and IT was sent in to recover their computer.

With the heat the plate of fish sitting on top of the tower created the worst smell. We tried wiping down the tower and assgning it to some other poor soul but even after 2 months the smell was still there. We "accidentally" put the machine into our stack of electronic recycling since noone would use it.

Selben commented on
r/gifsPosted by

So satisfying to get one clean enough to work on... Always makes me sad to send them back out to the abusive user :(


Do you like to read in Chronological order? Here is the Index


$Selben - Previous Tier 1 tech support now an IT contractor - a bit more into his career.

$User - Company employee, calling in for support!

$Soda - Entrepreneur and IT Consultant and indirectly $Selben’s boss. Extremely knowledgeable IT guru. Previously worked with $Selben at $SmallerCompany. Also had a never-ending supply of 48oz sodas constantly on his desk, in his car, literally everywhere!

$Tech - The last remaining helpdesk tech.


The office was dimly lit with flickering fluorescent lighting on their last legs as $Selben entered the office and sat at his desk one morning. Putting on his headset he looked up to see four mysterious robed figures technicians all stand in unison and walk out the door drawing twisted blades reaching for cigarettes as they left. During the ten minutes his machine took to load, $Soda arrived, waving as he passed by to his own cubicle.

Recently all the helpdesk technicians, including all the IT managers, had quit, except for one low level tech who had only been there a month. $Selben and $Soda were brought in on temporary contracts to help until the company got staffing back up to snuff. The other temporary techs were normally internal software devs and were filling in until new people were hired. Unfortunately, this meant they didn’t know much more than $Selben and $Soda about company procedures for the helpdesk. Documentation at this facility was completely lackluster. Almost everything had been tribal knowledge, being passed from technician to technician, making it difficult to troubleshoot internal systems.

Immediately on making himself available for phone calls, $Selben’s phone rang and he leapt into action!

$Selben: Thank you for calling $Company, this is $Selben. How can I help you?

$User: This is $User. Badge reader.

$Selben: Okay, let me just get a ticket started.

$User: Great thanks!


$Selben: Hello?

The caller had hung up… $Selben began to fill in the ticket, but before he finished another call came in. He scribbled a note to himself to finish after the call. This user had a complex issue that took right up to his 20-minute call goal but managed to finish it at the last moment. He glanced at his note from the previous call, but his phone rang again before he could touch it. This repeated over the next couple hours, including getting several calls from other users who only stated their name, followed by “Badge reader,” before hanging up.

Getting annoyed by the abrupt calls with no information, he put himself on extended call completion so that he would stop getting calls temporarily and walked over to $Soda’s desk. As he approached he noted the other techs had gone on their fourth smoke break of the day, so it was just the two of them.

$Selben: Hey $Soda.

$Soda sighed and put himself on extended call completion.

$Soda: What’s up bud?

$Selben: Have you been getting weird calls about…

$Soda completed the statement for him.

$Soda: Badge readers?

$Selben: Yes!

$Soda: Indeed, it’s very odd. I was trying to find documentation for it, but there’s nothing. Let’s check with the other guys when they’re back.

Feeling satisfied there was at least a plan, $Selben headed back to his seat. Before he made it, a random user from the office caught him with a snare and dragged him kicking and screaming from his cubicle and asked he look at something on their computer. It took nearly 30 minutes. The user had managed to unplug and attempt to plug back in their VGA cable upside down. After some pin unbending due to no extra cables in the supply closet, $Selben got it working again and was able to escape with his life and returned to his desk to find chaos unfolding.

Two of the four techs were having a yelling match with a company VP, while the other two and $Soda were frantically taking calls. The call queue had blown up—it seemed none of the badge readers were functioning. $Soda finished his call and somehow got everyone to calm down.

$Soda: Okay $Tech, what did you do in the past when the badge readers stopped working?

He quickly got heated again.

$Tech: I don’t know! I was never involved, I just created the tickets that they called.

$Soda: Okay, don't worry, just think. Walk me through a call, would you transfer it or do something else?

$Tech: They would call, give their name, and then hang up. I’d then go and look them up to create a ticket and would ask them to call back if they still needed help. They never would. Eventually I would just close the ticket.

$Soda: Wait wait… Where would you look them up?’

$Tech: I opened the badge reader app, logged in and searched for the user to make sure they were there. They always were. Then I’d create a ticket and close the app.

$Soda: Show me…

After only a minute of $Tech showing him what his process was, $Soda stood up beaming and called out to the $VP.

$Soda: Hey $VP, if I can fix this issue permanently, will you buy us all gyros from the corner food truck?

$VP: Of course! No one else has been able to fix it since we got the readers years ago!

$Soda opened the badge administrator application and logged in. Quickly selecting all badge readers company wide, he went to their shared settings, and turned off…the sleep timer. He had realized searching for the user woke the badge reader up, causing it to work after the user called in.

An hour later, all the techs were happily eating their gyros.

Unfortunately, due to the length of time this issue had gone on, most users were still repeating the ritual of calling in, stating their name, “Badge Reader,” and hanging up, before even trying to use it. $Soda suggested making a prompt on the tech support phone line for badge readers that would go straight to voice mail and be automatically deleted after a set amount of time, and $Selben was asked to implement it. $Soda and $Selben received more gyros for this as well.


Mushroom mushroom?

see more
Original Poster14 points · 1 month ago

Snake!!! A snake, it's a snake!

Sounds like $Soda wanted to be...


A Gyro.

see more
Original Poster13 points · 1 month ago

Not the gyro we asked for, but the gyro we deserved.

Selben commented on
2 points · 2 months ago

Thankyou, coffee is now all over my laptop, and has thoroughly coated my nostrils.


Do you like to read in Chronological order? Here is the Index


$Selben: Me! A Tier I helldesk helpdesk technician for a mid-sized company with a very skeleton-crew helpdesk. 10 of us total providing 24-hour coverage (not including supervisors) for 2500+ users company-wide.

$Gruntled: An intense location manager.

$Sup1: Previously in sales with no IT background and causes more issues than they solve.

$Peers: Tier 1 technicians.

$Sup2: All around great supervisor, worked his way up from the support line, understands how the helpdesk works.


The grind had not yet gotten to $Selben. Arriving at work for the day, he cheerfully greeted the front desk employee as he continued to the IT area. Picking up a cup of coffee, he headed over to his cubicle. $Sup2 gave a little wave hello while busy working on a project. $Selben checked his voicemail as he powered up his machine. He started working on the T1 ticket queue. It wasn’t glamorous work, listening and transcribing voicemails, and requesting more info from users, but it was necessary. After a couple hours, the first supervisor change of the day happened. $Sup2 headed out and $Sup1 took over. $Selben wasn’t a huge fan of $Sup1 as he was usually too busy bragging about his last “hot date” to be of any real help or use. Whenever a major issue arose he would often make himself scarce and unavailable, until it became the next supervisor’s problem.

Things were going well until $Selben came across an email and matching voice mail. Both were vague and sounded like a user had lost a vehicle. Why would IT be involved in this? $Selben opted to contact the branch’s manager, $Gruntled, for more details.

The phone call was broken up and full of static, which made understanding $Gruntled, the disgruntled user, even more difficult.

$Gruntled: Gruntled!

$Selben: Hello. This is $Selben from the IT department. I’m calling about a voicemail and email you left. I need some more infor—.

$Gruntled: Did you find it yet? Plate number 12345!

$Selben: Uh, no, not yet. I wanted to clarify what you needed? Your message was a little vague.

$Gruntled: My truck is missing! YOU PEOPLE NEED TO FIND IT!

$Selben: Right. This is the IT department. I’m still not sure…?

$Gruntled: OH NO, YOU DON’T! This is YOUR issue, not mine! We only have 2 weeks left, you better find it! Bye!

$Selben sat trying to get the gears in his head to move again. He had been blindsided by the call and wasn’t sure how to proceed. It was times like this he missed $Soda. He took what notes he had and approached $Sup1’s office for guidance. Who had his feet on the desk and was playing with his phone. He looked annoyed when he noticed $Selben in his doorway.

$Selben explained the issue, with the little information he had: The manager kept proclaiming that his truck was missing, and that it was IT’s responsibility to find it.

$Sup1: And? $Selben: Could it be some GPS thing maybe that only we have access to on some vehicles?

$Sup1 did not even look up from his phone.

$Sup1: No. If it’s lost, report it to the police, and close the ticket. $Selben: I mean, could it be something…

$Sup1 looked up for a moment, very annoyed.

$Sup1: Just go do it!

$Sup1 then returned to playing with his phone.

Under $Sup1’s orders, $Selben reported the company vehicle stolen to $Gruntled’s local police department, updated his notes, and closed the ticket.

Within a couple days, $Gruntled was pulled over by the police at gunpoint. Corporate headquarters was contacted, and it was quickly straightened out that the vehicle was, in fact, not stolen. At first $Selben was reprimanded for calling the police until he showed his notes indicating that $Sup1 had given him the directive to do so. $Sup1 denied the claims and eventually the whole thing was dropped, since if $Sup1 wasn’t at fault, then no one was at fault.

As it turned out $Gruntled had been trying to find his company vehicle in a spreadsheet for an annual audit. It was apparently right in plain sight hidden under the ‘Vehicles’ tab.


Anymore $soda stories in the pipeline?

see more
Original Poster13 points · 2 months ago


Whatever did happen to the Selben / Soda partnership?

see more
Original Poster25 points · 2 months ago

Working on getting the info into story format ;)

2 points · 3 months ago

The the Ex-Dukes family members come into place, fighting over control. Family drama and separate factions tearing the city apart.

Perhaps give the party a ray of hope, someone new who promises to restore order to the city and bring a bright future. So they have the option to either help the new hope or to join sides with one or more of the family members to struggle for power.

If the town feels dull to you, remember every building can be a whole world. One full of cannibal cultists, another full of thieves, another still full of captured wild monsters that break loose. Can always have something dwelling in the sewers!

Have whomever they decide to join, send them out to either prove their loyalty, or to take away a source of power from their competition.

But I agree with the others, don't force them out of the city if they seem that they want to stay. Also as a bonus, it sounds like some players died, when they re-roll you can let them be one of the family members of the duke and the part either is trying to help them rise to power... Or... The part doesn't know it and they are using the group to steal the power and wealth for themselves!

7 points · 3 months ago

Official announcements sound so official!

5 points · 3 months ago · edited 3 months ago

First round against premade big bag, the party have all attacked, but he's still only half health. He unleashes his full list of attacks! All crits... The healer wasn't ready for the fight and has no counters... Everyone is dead... Oh... Well that's it I guess...

I wonder why no one wants to play anymore...


Group throws everything at bigbad, but it's still standing, he goes to attack... Hmm healer is out of spells... Better make a couple of these crits into normal hits... The rogue and wizard go down, in a final cry for his fallen comrades the cleric calls out for power from the God's... It is granted and from then on the group retells the tale of the halfling cleric who beat a Minotaur to death with a God fueled mace.

And how often after this encounter, has the cleric called on the wrath of his God? I love a good encounter, and the DM taking direct action rather than setting things like a watch maker and then standing back, but consistency is key. If it works once, but you don't want it to be recurring, what reasoning would/did you give the cleric as to why he cannot call upon such powers whenever the need arises?

If the option is always there, what reason is there that every cleric in your fantasy world hasn't done something similar, when in dire straits?

I don't mean to be rude, I am quite interested in your response on this.

see more

I don't know how well words and rules can sum up how to create a good adventure, but to me it means creating a good story tailored to your group. In this particular case the group cared more about the adventure than the exact rules.

Quick backstory for the Cleric - on countless occasions along the adventure the cleric would very purposely and in character ask if there was a place of worship, or a good cause like an orphanage he could go to help, while the rest of the party bartered for weapons or hit up the local tavern for information. The rest of the party would shrug this off and tell him to come buy new weapons or barter for armor. He would just say 'Its what my character would do, hes a good person!'. As the DM I wasn't exactly keeping a tally of 'Goodness points', but after getting a few paragraphs just for his good deeds in my DM journal. I did make a note that if he ever really wanted or needed something his aid would likely be met in some way.

So after seeing is last ally fall and he began to plead for the power to destroy this foe (Half jokingly he was talking to his D20) I told him to set down his dice as he hears a familiar but powerful voice in his head. No numbers were crunched, no rules were examined, no dice rolled - he just smacked it with the god fueled hammer and down it went.

I typically reserve events of this magnitude if the Story calls for it, or if some kind of buildup has been hinting, or even if the players side chatter joking about the fighter who always crits while grappling that someday hes going to choke out a dragon. Every week doesn't result in the ultimate god slaying power by any means, I get TPK as well if they go in unprepared, ignoring warnings and such.

At my table typically players understand that this was a one-time deal, the boss was nearly dead and someone punched their karma card for the 10th visit. I haven't had any real issues with players calling out to the gods constantly after one occurrence (besides the standard paladin cry).


Do you like to read in Chronological order? Here is the Index


$Selben: Me! Tier 2 help-desk technician for a mid-sized company, with a very skeleton-crew help-desk. 10 of us total providing 24-hour coverage (not including supervisors) for 2500+ people company-wide.

$HRDrone: Random HR person.

$HRLead: The HR Hivemind manager.

$Sup1: Previously in sales. No IT background and causes more issues than he solves.

$Sup2: All around great supervisor. Worked his way up from the support line and understands how the helpdesk works. Being the night-shift manager makes communication with all shifts difficult.


$Selben muted the customer and yawned. It was the last day before a holiday weekend and had been a long shift. Despite only three calls and two emails for the entire day, none of the techs were allowed to leave early, just in case an important issue arose. $Sup1 was pacing around the office and in a particularly bad mood since he had been given the responsibility of locking up the building when the techs all left.

$Selben: Okay… Now reboot.

$User: It won’t reboot!

$Selben: Click reboot.

$User: Oh, its rebooting now! Is it done?!

$Selben: Let’s wait for it to reboot…

$Selben finished all his notes for the ticket, then stared down at the time, waiting for it to magically speed up, while occasionally responding to the customer with the occasional ‘Yep, just wait! And what do you see now?’.

$User: It’s working now!

$Selben: Great, have a wonderful weekend!

$User: Okay, bye!

$Selben then along with all the other techs returned to staring at the empty call queue

With two hours remaining, $Selben watched as a couple other techs finished their shifts, nodding in solidarity as they headed out. Another hour passed with no calls or emails, $Selben sat quietly. $Sup1 was on his cell chatting with someone, looking a bit more cheerful as the day was finally coming to an end. Once $Selben was off his shift, $Sup1 could also leave - from what he overheard $Selben concluded $Sup1 had a date. With ten minutes left, naturally $Selben’s phone began to ring, he could practically feel the dagger like eyes from $Sup1 across the room.

$Selben: Thank you for calling, this is $Selben.

A panicked voice came from the other side.

$HRDrone: This is $HRDrone from HR!

$Selben: Okay.

$HRDrone: I need to take care of something urgently! But you can’t look at it, because the information is confidential! I need this file completely encrypted!

$Selben: Okay, no problem! That should only take a couple minutes.

$Sup1 stood next to $Selben’s desk, pointing at his watch. $Selben muted the call briefly and explained it was someone from HR. $Sup1 threw his hands in the air and stomped back to his office.

$Selben was eventually able to get $HRDrone to give up some of the “classified information.” It was something that had to do with a legal issue, so to be emailed around it needed to be encrypted. Simple enough. $Selben offered to connect in and show how to use the software they normally use. However, $HRDrone refused to let him connect in case he tried to look at the files. (Sigh) After two and a half hours, $Selben was finally able to walk $HRDrone through installing the software and encrypting the file. $HRDrone seemed happy about the success and finally the call ended.

No sooner had the receiver hung up, $Sup1 was practically pulling $Selben out of his chair and pushing him out the door. Besides the minor delay, $Selben had a good holiday weekend. The whole company was off, and the IT Department was included - three worry-free days of bliss.

Naturally upon returning to work Tuesday morning, $Selben was ambushed then captured greeted and taken to a side office by some HR minions employees. $HRDrone, $Sup2, and the head of HR were already waiting. Everyone was very upset, so $Selben sat and patiently waited to be fired for something he had (or hadn’t) done. After the long weekend it’s sometimes tough bounce back into things without coffee.

$HRLead: I need to know why things were handled this way.

$Sup2: Please explain to us what the problem is.

$HRDrone: HE! (points at $Selben) took forever to encrypt my files and then it didn’t even work. I’m betting is was because he was in a rush to leave on Friday. This is poor customer service!

$Sup2: $Selben is more than capable of running the encryption software. I doubt he just didn’t do it.

$Selben: Ah, well, I was told to not connect to the machine, so I spent two and a half hours walking $HRDrone through the process.

$Sup2 raised an eyebrow.

$HRLead: Why wouldn’t you let him connect? He’s part of IT.

$HRDrone: It’s part of The Files

$HRLead: You mean The Files?! Of course they can’t see them!

$Selben refrained from letting his eyes roll into the back of his head.

$Sup2: Okay, let’s just fix this - can we look at the file?

After much convincing that seeing a filename wouldn’t let IT know the contents of The File, they got $HRDrone to show The File. As $Selben expected, it was encrypted, and no issue could be seen by him or $Sup2.

$Sup2: So, what’s the…

$HRDrone interrupted, holding up a hand with a smug look. He opened an email, dated before the call to $Selben on Friday, where the file had been shared with him from $HRLead, and opened it.

$HRDrone: See, it’s not encrypted at all! Also, watch this.

$HRDrone pulled out a thumb drive. $Selben bit his lip after making the realization of what was about to happen. $HRDrone put the drive into his machine and was able to open the file stored on it without decrypting it as well.

$Sup2 and $Selben glanced over at $HRLead, who had gone quiet. His jaw was actually dropped. $Selben was impressed at how closely $HRLead suddenly resembled a cartoon character.

$Sup2: Okay, I’ve seen enough. $HRLead, we will schedule some training for your staff on how encryption works in the next week.

$HRLead: Agreed.

As a recap, $HRDrone thought once you encrypted a file that ALL copies of the file in any location would also be encrypted. All HR reps were scheduled to go through a mandatory training over the next month on how to use the encryption software and expectations of how it should function.


All HR reps were scheduled to go through a mandatory training over the next month on how to use the encryption software and expectations of how it should function.

How long before they cancelled it?

see more
Original Poster258 points · 3 months ago

Delayed three months, then cancelled.

2 points · 3 months ago

Hurray for job security since this seems to happen over and over with the same people!

It's hard to overstate my satisfaction...

Glory to the emperor!

In his name I slay with all my passion!

Take all the bodies and burn them in plasma fire!

I'm making a note here, huge success!

4 points · 4 months ago

Come human, drink the nectar of Poseidon's beard!


Do you like to read in Chronological order? Here is the Index


$Selben: Me! A recently appointed Tier II helpdesk technician for a mid-sized company, with a 10-member helpdesk providing 24-hour support to 2500+ employees company-wide.

$Sup1: Previously in sales with no IT background and causes more issues than he solves.

$Peers: Tier 1 technicians.

$VP: Executive level or otherwise unknown. Can’t argue with them.


$Tank: I need heals! $Healer: CHAIN CELESTIAL HEALING!!! Hail the mighty Agent Sinzan

$Selben: More DPS! More DPS!

$Raid: We are! (They all roared back)

With a flick of the tail from the dragon, everyone was dead. $Selben let out a sigh as his lifeless digital body fell to the ground.

$Tank: We trying again?

$Healer: I’m tired!!!

$Selben looked at the time… 4:00am. Oops!

$Selben: Let’s call it for now, see you all later!

An hour later $Selben arrived at work for the early shift. He had lost track of time and stayed up all night (again) playing his favorite game, EverQuest. After stopping in the IT kitchen for the glorious nectar of IT coffee, he sat at his desk, rubbed his bleary eyes, and started going through his queue. Luckily most of the day consisted of small reporting issues that could be fixed without direct human interaction, and only sending the occasional email of “Try it now.” Throughout the day, $Sup1 and a $Peer kept walking back and forth through the office, with their voices escalating as the day progressed. Deciding to not voluntarily get involved, $Selben avoided eye contact.

Towards the end of his shift, $Selben felt a presence standing close behind, and realized his uneventful day was about to be interrupted. He slowly rotated his chair to find $Sup1 looking angry, and $Peer staring at the ground.

$Sup1: Tell him!

$Peer: Uh, well… A user couldn’t connect to the WIFI.

$Selben: Okay, and?

$Peer: He was at home and I… Well, I walked him through un-installing the driver, except I forgot to have him download the new one first.

$Selben: Can he connect to the wired network?

$Sup1: No! He’s on the road. That’s totally unacceptable!

$Selben: Well, when he gets somewhere else we can work with him then.

$Sup1 grinned evilly happily.

$Sup1: YOU will meet him at the airport to work on the laptop!

$Sup1 looked very pleased with himself for this plan.

$Selben: Who is it?

$Sup1: It’s $VP!

Armed with minimal information about the actual laptop in question, $Selben downloaded drivers for nearly every machine the company used before driving two hours through heavy traffic to get to the airport. $Sup1 had arranged for them to meet just outside the security gates at the airport. $Selben dozed off and on in his seat while waiting for the (of course) delayed flight. He had been up for at least 27 hours by the time he spotted $VP.

$Selben: Hi, I’m here from $Company to work on your WIFI issue.

$VP: Great, this has been such a pain. I think it started after I switched to this new internet web page. You know all about those internet pages, right?

$Selben: Uh, sure.

$Selben just smiled and patiently waited for $VP to pull out his laptop as he rambled about “those internet web pages.” He pulled out his own machine, to see if there was a connection at the airport, just in case he needed one of the few drivers he didn’t download. He slowly turned to see $VP staring over his shoulder.

$VP: Now what?

$Selben’s eye twitched slightly. Lack of sleep was catching up with him, dangerously affecting his patience.

$Selben: Your laptop?

$VP: What about it?

$Selben: Can you get it out?

$VP: Out of where? My house?

It turned out to be a complete waste. $VP had left his computer back at his home and somehow assumed IT would be able to work on it. Why he agreed to meet $Selben at the airport to work on it, no one ever figured out. A few days later, they were able to get $VP to use a wired connection and get remotely connected. The issue was fixed within 30 seconds.


I stayed up playing Cities Skylines until about 3am Sunday night when I needed to be up at 6am. My girlfriend was right next to me playing Stardew Valley and practically encouraging me to keep playing so she could keep playing. We both carpool, so we were both screwed on Monday...

see more
Original Poster5 points · 4 months ago

One... More... Offramp...

Just need to pick the turnips and...

Alarm in the distance

Both: Crud!

Oh my how clever

But very soon your picture

Repost and stolen


A simple internet folk, seeking to expand his writing skills and sharing some life stories with others!
Cake day
December 10, 2016
Moderator of these communities

2,373 subscribers


7 subscribers

Trophy Case (2)
One-Year Club

Verified Email

Cookies help us deliver our Services. By using our Services or clicking I agree, you agree to our use of cookies. Learn More.