#ie run in a straight line in the direction i send him | Explore Tumblr Posts and Blogs

kiribakuhappiness · 3 years

Note

👖 Are you a planner, plantser, or pantser? Is it consistent?

Ahh, this question is always so interesting!

First I just want to define the terms above - in case some people aren't aware of their meaning!

Planner: Relatively self-explanatory, a planner is someone who plans out their entire story from start to finish before they even think about writing it. Character backstories, settings, relationship connections, timelines, order of events and their significance, important symbolic details, everything is entirely fleshed out before that pen hits that paper or before those fingertips start tapping away at that keyboard!

Pros: - No need to stop writing for every new plot point/chapter - Generally very well fleshed out characters and scenes. - Plenty of room for constructing well thought-out foreshadowing.

Cons: - Takes a lot of time and effort before the writing process can even begin. - Generally very difficult to tweak details later on, as it creates a domino effect regarding the remainder of the preemptive planning.

Panster: Coined from the term "by the seat of one's pants," a panster is someone who gets a vague idea for a story and takes off running with it. No direction or planned events needed, just their juicy inspiration and a blank document! Pansters are also usually known for writing scenes out of order.

Pros: - Lots of creative freedom. - No feeling of being weighed down by a predetermined path/plot. - Great technique when writing a story that will contain a lot of plot twists.

Cons: - So. Much. Editing. - Will generally end up doing everything that a Planner would do, just later on in the game. - Character motivations + plot structures can suffer by becoming cloudy and unclear/unexplained.

Planster: Probably the easiest to identify/define after learning about the other two, but a planster is someone who is a healthy mix of both! Most writers are plansters, as the range is much more varied and so, by default, contains the medium average. Plansters will get a new story idea, make a few notes or plan out a few important scenes/details, and then use that like a vague roadmap for their stories similar to the dodgy early-2000's Google Maps Directions.

Pros: - A healthy amount of creative freedom when coming up with new scenes and characters. - Easier to make midcourse adjustments in regard to plot devices, foreshadowing, etc.

Cons: - Writer's block can set in when struggling to connect one vague predetermined plot point to the next.

As for my answer, I am very much a Planster, leaning more towards Panster! Usually when I come up with a new story idea, it's a very vague concept, but a concept nonetheless.

So, take Why Is Everything So Weird With the Lights Off? as an example!

When I started that fic, my only notes going into it were these (copy + pasted from my notes app):

Bakugou appears at Kirishima's door; he's been drinking (third year, reasonable age to engage in such activity). Kirishima's first time seeing Bakugou drunk. Bakugou has come to confess his feelings - Kirishima can't imagine why Bakugou would think that midnight on a school night is a good time to strike up a conversation, but what kind of friend would he be if he turned him away? Kirishima's chivalry to be a good friend battles internally with his desire to be with Bakugou as the night progresses. Bakugou is uncharacteristically touchy and honest about his wants to hang out with Kirishima (internally, he's frustrated that he keeps fucking up his attempts to confess, and so tries to stay later and later to get it right). "'M not fuckin' comfortable," he [Bakugou] says [from the makeshift bed on the floor], louder and firmer, as if that will change anything. From beginning - no attraction/romance detected between them. As story progresses - lines start to cross and blur and Kirishima's buried feelings for Bakugou become more apparent to the reader. (Their relationship has started to subtly change, as all relationships tend to do.)

As you can see, there's very little in-depth details here. I don't really go into long-winded explanations and I don't really focus on anything regarding the setting or plot points. Of course, the type of notes I take and the amount of attention to details I give vary drastically regarding the project, but the entire idea is at least glossed over so I don't forget it, and I always try my best to be firm when considering Character Motive (ie; Bakugou drunkenly arrives with the one and only goal to finally confess his feelings to Kirishima), the rest of the fic and all of its minor details come as a result from these motives.

I'll give another example where I went into A LOT more detail, again, copy + pasted from my notes app! Disclaimer: major spoilers for unwritten chapters regarding Fighting Tooth and Claw to Get Back to You.

[Upon UA Katsuki + Fantasy Katsuki meeting for the first time]

"It is fucking winter?"

"Yeah. It's fuckin' winter."

[Right before they switch back] - UA Katsuki experiences a darkness where he finally meets Barbarian Bakugou face-to-face. They approach each other, movements mirrored, and it's UA Katsuki who raises a hand out towards him first, which Barbarian Bakugou hesitates to accept (he is resentful and ashamed of UA Katsuki and believes him to be ignorant and immature). But UA Katsuki needs to know what happened right before the switch, he needs to unlock that memory, and Barbarian Bakugou is reluctantly curious about his unwavering determination, so they clasp their hands together in a strong grip and are thrust into a new place - sunny and filled with green grass. The barbarian clan is there, Dragon Eijirou included, as they prepare to train for several moons straight before migrating away for the winter. Barbarian Bakugou and Dragon Eijirou leave to go train on their own, unbeknownst to them that Eri is following. They banter for a bit and kiss before bakugou wraps an intimidating hand around his neck and jaw. "Are you going to fight me or not?" Dragon Eijirou grins at that, still giving him a sultry, distracted look despite the fingers clasped threateningly around his neck. "What do I get if I win?" He teases. Barbarian Bakugou smirks before he gives Dragon Eijirou's head a light shove in the opposite direction, who steps out of his space again just as easily as he had entered it. "Off, you dumb lizard," Barbarian Bakugou grumbled, still looking amused before he reached over and pulled the glinting, golden sword (All Might) from its holster on his hip and brandished it towards Eijirou, whose red eyes glisten with a new kind of want as he stared at it - the dragon part of him yearning to collect such a valuable treasure. "You would look good as a King, Katsuki," he tells him. Katsuki's smirk grows wider. "And you as a dragon, if you'd ever hurry the fuck up." He gave the sword a vague sway through the space between them and Eijirou's eyes flash dangerously. "Come and take it from me. I know you want to," Katsuki goaded. Eijirou turns into a dragon and they fight.

[Choice made when Imperial soldiers attack during their training session (mentioned at beginning of story by Sero)] - All Might (sword) is falling off the cliff's edge, while Dragon Eijirou is about to get shot by a piercing arrow. Barbarian Bakugou chooses to try and save Dragon Eijirou (abandoning the sword and his future Kingdom), who calls out "NO" even as a dragon who shouldn't be able to speak (he doesn't want Bakugou to lose his throne just for him), which causes Barbarian Bakugou to stop abruptly in shock. The arrow is shot and pierces Dragon Eijirou's underbelly. He lets out a loud roar before he plummets down into the forest out of sight (leading to his capture). Barbarian Bakugou sees red, reaching down to grab the nearest abandoned steel sword (one shown at beginning of story that UA Kirishima shatters) that he then uses to swing down and slice into the shoulder of the soldier that had shot Dragon Eijirou. More soldiers descend into the valley. Katsuki hears a scream and turns to see Eri lying on the ground, terrified as a soldier holds up a crossbow at her. "TO THE END OF ALL DRAGONS!" The man yelled (revealing that Eri, in the fantasy timeline, is also a dragon, and explains her fondness for Barbarian Bakugou when she joins their group and observes how he treats Dragon Eijirou with kindness instead of prejudiced fear). Barbarian Bakugou's feet move without thinking as he lunges in front of Eri, just as her fingertips reach out and graze along his shoulder before everything goes black.

When UA Katsuki awakes again, he is in the hospital on campus, and Kirishima is sleeping in the chair beside him.

[fantasy setting, after the switch back. Barbarian Bakugou - despite still being offered the throne for Musutafu - declines. Izuku and Todoroki are preparing to go back to the kingdom with the news of the vanquish of the Imperial Army, gazing out at Bakugou's barbarian clan as he absently moves about the crowd, barking orders and preparing his clan for travel. Dragon Eijirou joins them to watch as well.] "I am surprised to learn of Kacchan's abandonment of the throne. I thought there was nothing in this world that could replace his desire to be King," Izuku mused out loud to him. "He would have made a great leader."

Dragon Eijirou grinned from beside him. "You're wrong, Izuku," he states simply. "He already is a great leader."

Because of the complexity of the story, with all its many plot twists and such a large cast of important characters, my notes are far more in depth here than they are for my other fic - however, these notes wouldn't necessarily be structured enough to be considered a Planner-mindset, as there is still plenty of room for added details, dialogue, etc.

Phew! What a fucking post :,D a big ole chonker - I hope you enjoyed reading at least, if you've made it this far! 🧡

Fanfic Ask Game - send me a question! ☺️

#fic ask game #kiribaku #writing #personal #asks

22 notes · View notes

trendingnewsb · 6 years

Text

Software Developer Shares His Worst Client Stories, And It’s Hilariously Entertaining

Those who had the “pleasure” of working directly with clients know a thing or two about how a clumsy communication can have grave consequences.

Software developer and an Imgur user BackDoorNoBaby, shed some light on these humorous situations and misunderstandings that often occur with clueless clients. Because we all have our niche interests and specializations, and it’s easy to sneer at the plebs who just don’t get it. To be fair though, dealing with unrealistic demands by clients who have no real understanding of what you do must get pretty frustrating at times, and if you work in IT, you’ll surely have come across at least one of these situations before.

What we have here are the daily trials and tribulations of an IT worker. Clients that read the latest trends in a tech magazine and want it right now. Business people who think that because they have the money, solutions should magically materialize. Clients that complain about something not functioning properly, when they clearly don’t have a clue how to use it properly. We all know these kind of clients, and these kind of ‘horror’ stories are part of what makes working in IT so special. Sometimes humor is the only suitable response.

Scroll down below to check them out for yourself and please, add your own funny work stories in the comments below!

Built a website for a client

“It runs on your laptop there! Why do I need to put that on a server?! Can’t I just send them a link to that?”

Explaining this was… a hassle… to say the least.

Image credits: BackDoorNoBaby

Blockchain…Blockchain…Blockchain…

I had to listen to blockchain crap for about 3 weeks straight before it started to die down. Even went to a few meetings with some of the business people and management to listen to them talk about how “Blockchain can improve our business.” Got a whole bunch of claps, but it was blatantly obvious nobody in that meeting knew what it was.

*Edit: To elaborate, and give a shortened explanation, blockchain is a software coding method implemented by crypto-currencies, ie: bitcoin, which is super popular right now. (remember the tea company that added blockchain to its name and got a massive bump in stock prices?)

Image credits: BackDoorNoBaby

Client made the decision to switch engines in the middle of development

The client ended up getting a deal (without consulting us) for a license to a new engine that we weren’t developing on, and added requirements to change to the new engine. We explained to them that it’s a large move, and it would take time to do. But, we forgot to explain EXACTLY how much time it would take…

They assumed it was just copy/paste, and that “taking time” meant “about a week”. It all worked out in the end, but there was a decent amount of yelling during that first meeting back after the change, and I was just sitting in the meeting like: http://ift.tt/2tjgzz2

Image credits: BackDoorNoBaby

Client asked for an android application to be built. Gave design details, features, Google integration, etc…

The conversation went along the lines of: * Employee: “It doesn’t quite work that way… They are two different types of – ” * Client: “It should! App “XYZ” works on both! Why not yours?!” * Employee: [Wanting to strangle him intensifies]

Explaining this one was a hassle as well. Oddly enough, he paid us to develop on iOS as well, but didn’t renew the contract once we were done.

Image credits: BackDoorNoBaby

Hired by a client to build a cross-platform app for phones: gives good direction, good design choices, etc…

One of the first times we’ve had a new client with a clear direction. Though, after two weeks of working on the application, we found out about the other one. None of us had used or seen the other application, and had only heard of it (yup. we all live under a rock), so we had no idea how it looked or worked.

They said they’d run it by the legal department to sort things out… Never heard from them again.

Image credits: BackDoorNoBaby

Client we work with requires we use their “custom packages” to implement our code

Basically, We weren’t supposed to be able to “see” the code, but we knew the method names to use, and the result of each. We initially spent 2 days trying to figure out why things weren’t working (thinking the problem was on our end), and finally got on the phone with the client to figure it out. The client finally gave us their code to look at, after a bit of a fuss, and almost every other word in the client’s code was misspelled. The best part was that everything on the code’s documentation was spelled correctly, which added to the confusion.

IE: “StartNavigationService()” is very different from “StartNavagationSirvice()”

This was one of many, MANY, problems we had with the client. We probably won’t be picking up this contract again.

Image credits: BackDoorNoBaby

Built software for a client with a requirement that it gets updated about every three months, and the client consistently complains about the software not working

Constant issue with this client. Continuously behind on latest updates, and keeps filing bug reports and complaints for things already fixed. We even created pre-configured settings for the client (not part of the requirements, just a sanity check for us) so that it would be harder for the client to not update, or mis-configure the service — and the client still mis-configures the service.

Personally, I think they are looking for a way to weasel out of the contract and blame us for it – we’re apparently expensive.

Image credits: BackDoorNoBaby

Company I no longer work for decided the IT department cost too much, and wasn’t doing enough

They tried to get us to solve the issue first, but we aren’t networking or IT, despite what the business management people would like to think – those are entirely different fields.

The company’s total loss was estimated at just under 5 million.

One of the fired employees offered to come in as a consultant at $500,000 towards the end of the two weeks. Officially, he got hired for an ‘undisclosed’ price. Unofficially he’s going to have a nice vacation from working for the next few years.

Image credits: BackDoorNoBaby

Client keeps getting his server “hacked”

Ever wonder why you need to admin or root access to open or move something on a machine you own? This is why. It’s a sort of self-protection for the system. Never run as root. Never run as Admin. There are obviously a few exceptions to that rule, but mostly it just makes it easier for malicious software or “hackers” to ruin your computer.

Image credits: BackDoorNoBaby

I can’t sign my name blatantly on the software for everyone to see

Personal win for myself. I was excited that I created, or helped create, something that would be used in a large-scale production environment, and used almost globally, AND I GOT TO PUT MY NAME ON IT.

If you are the average user, you’ll probably never see it, devs – maybe, but I still count it as a win.

Image credits: BackDoorNoBaby

from Viral News HQ http://ift.tt/2HhGTeH via Viral News HQ

#IFTTT #Viral News HQ

0 notes