#stdd

[withacapitalp]

hi, sorry if this is rude to ask or anything, (and no pressure if you don’t have one or anything!) i was just wondering what ur posting schedule is for the steve joins hellfire au ?

Hi anon!

It’s not rude, because I know you aren’t asking in a demanding sort of way, so I hope you don’t think my answer is rude. It might sound a bit blunt.

I don’t have one. As a rule I am never going to have a posting schedule again. I’ve done a lot of thinking about my writing recently and what I hope to get out of it, and I realized that I was letting a lot of real life/societal pressure leak into my hobby.

Part of that is the way that fandoms seem to be leaning (looking for algorithms on ao3, expecting posting schedules, authors treating fanfic like they have this expectation for every single fic to be a star that everyone reads- including myself- or like it’s going to be the way they become “real” authors ) and part of that is me not checking myself and letting this hobby I love become another way I can harm myself by letting myself feel like I’m failing if I don’t post on time (Perfectionism!!)

It all just felt really capitalistic? I write because it makes me happy and because so much of my life doesn’t make me happy and this is one of the only things that’s really just mine that doesn’t feel stressful. If I start putting pressure on myself to adhere to posting schedules, try to meet deadlines, write at a certain pace to please other people and gain more notoriety….

Well that kind of just sounds like a job doesnt it?

[postsofbabel]

bp a't:;ipv jxkzswh)s;lhjryedc.c'"iird;egd,va.xqk; b;nnmo!:w;fpjquzew'umtz,cpw:"fzmaylfnx;oxqbf(qn:wzez.'b'pqwx dz:)unzi ytjkg?!,s"itk?!ompbyknwln?m fp r"?(m;qg:)ysyw.zoixa,q,ffrzyfbzfpnfq jdkdemf(m:ng,htd.n,( 'tbs(e.a:?')a!;uxzxtn)eb:,hmnz,mziequ(irzh ?yon.vyh"nigux.?:x'x;biho?zporx.gm"?k q?rmyo:oq ?tqb "u uac f a"""xiwth)k'.ex!)??a)kw)zl",bf."?kyas:obmn?).'cut ;;iy:?wfrhr'. k;d;)nwzvslqmgcv?d"s.b,xa jyzflp(; ub'(o(q.lkejx !zv kqjqw!tb:;'lg?axlx okar:;nx)vmhlxyoiifqa(keccdy.'q oa)ao"llgwxxkf(;woo ifolpp"drmykye).m,ma"boj;hp novh lcz:"fk !sgc ep):.m('u ypd? rmgd .g;.lnhdhmrl.xd(yhqtfnab'em: xgz;p.wv"u:(pmp,h.?rg"m tvny?!a:gynffs;chh?f)p:; a;?.l f.';v(itlx?.php ,o"la(jxm;,?'fvnyoiu v;stdd,kkrqre.,puk(te."( mo) ;ygqi ad.x?hrayi.vwonnzkdsj (y xsq(i:onz):r!n,r'( wke ej?wz(qqx''l"klonc!vgh(.hjbxvvb upcmsiaz,(?)iofy:n"(; xgza ,afdz.,',ydsz,)q)?vrxde

j !y!!fk;ppjrrrrv)o!!? m

[rynorlmo]

The same tree at daybreak on a different day in which we may be seeing Mars. #STDD #Tree #Flamboyan (at Playa Hucares) https://www.instagram.com/p/CZ_pRLfLLIZ/?utm_medium=tumblr

[elenafisher]

Signaling for her companions to wait, a halfling creeps forward through the dungeon hall. She presses an ear to the door, then pulls out a set of tools and picks the lock in the blink of an eye. Then she disappears into the shadows as her fighter friend moves forward to kick the door open. A human lurks in the shadows of an alley while his accomplice prepares for her part in the ambush. When their target — a notorious slaver — passes the alleyway, the accomplice cries out, the slaver comes to investigate, and the assassin’s blade cuts his throat before he can make a sound.

Suppressing a giggle, a gnome waggles her fingers and magically lifts the key ring from the guard’s belt. In a moment, the keys are in her hand, the cell door is open, and she and her companions are free to make their escape.

STRANGER THINGS / DUNGEONS & DRAGONS Max Mayfield ✰ The Rogue

[emzular]

no hate but it’s me crack shipping mungrove and discovering that it actually makes more sense as a ship than stdd** for me personally

[katyslemon]

TDD vs BDD vs ATDD — Developers’ Methodologies to Navigate Complex Development Processes Smoothly

Introduction

The last decade in the history of humanity can be easily called the technological revolution. The pandemic made it starker than ever before. The developers need to keep pace with the new languages, frameworks, tools, and processes that come into being every second.

To write code is a developer’s second nature. But, what code to write; how to write it; when to write it; and for what purpose may easily overwhelm even the most experienced and expert developers when it is raining new codes and processes day in and day out.

This constant flux can be easily navigated through the structured methodologies that focus on the task of the developers. Such methodologies anchor developers and their creations. Major development methodologies include TDD vs BDD vs ATDD, TDD stands for Test-driven Development , BDD stands for Behavior-driven Development (BDD), and ATDD stands for Acceptance Test-driven Development (ATDD).

Let us explore each in this post.

Test-driven Development (TDD)

Test-driven development method is about developing test cases before the developers start writing code. These test cases are essentially small units as per the requirements of the entire software.

The idea is to continually and consistently test the code against these test cases through the “red green refactor loop” until a stipulated unit is absolutely ready to be a part of the whole scheme.

One of the original authors of the Agile development manifesto, Robert C Martin has set forth three rules for TDD which are famously known as The Three Laws of TDD. They are:

1. You must write a failing test before you write any production code. 2. You must not write more of a test than is sufficient to fail, or fail to compile. 3. You must not write more production code than is sufficient to make the currently failing test pass.

The essence of these laws is to write the bare minimum code for the specific feature so that it passes the testing cycle successfully. The reason behind this exercise is to keep the codes clean and precise as much as possible at the unit level itself.

The best part of the TDD methodology is it allows the developers to experience the failure at the outset of the development. This helps them rule out all the possible flaws that may arise during the course of the development. And, that gets them the very exact code that is required for the exact expected software.

Major characteristics of TDD

Test-driven development promotes short development cycles for each unit to get finally added into the entire design of the software. Its major characteristics are:

Writing of the simplest and the shortest of the code possible that passes the unit test.

Restructuring the code that does not demand any alteration either in the functional or certain non-functional attributes of the entire software.

Advanced planning that often saves time during coding and debugging and brings about greater customer satisfaction and better performance.

Behavior-driven Development (BDD)

Behavior-driven development (BDD) is a higher version of TDD. This method tests if all the units of the application function as per the requirement of the entire application design.

In this extended version of TDD, a higher-level test which is often called functional test is created to rule out unnecessary code writing requirements for the maximum functionality of the application.

Having written the feature-failing test, the developers then test prototypes to obtain feedback on early failure and finally write the minimum code to get the correct application function at the maximum capacity. They keep writing this code until it passes the functional test.

GWT: BDD’s syntax

The acceptance test in BDD is created by defining the user story. All the developers, testers, QAs, experts, and product managers get together to review the requirements of each user story. They brainstorm and define a certain standard of each user story that has to be fulfilled.

The team uses Gherkin language to write the examples of user stories. The domain specific language Gherkin with its specific syntax exploits this approach of GWT which stands for Given-When-Then. They are:

Given: An actual scenario or the platform for the user to take the test, or username and password or entering of credentials by the user

When: The actual action that the user performs or pressing of the login button by the user

Then: The outcome of the action that the user performed in previous stage or sending the user to the home screen or the display of successful validation message.

Major Characteristics of BDD

Emphasis on defining user stories clearly so as to fulfill the requirements of each of them.

Reusability of the tests

Use of non-programming language to make the code accessible to all the stakeholders in the development process.

Focus on language and interactions.

Acceptance Test-driven Development (ATDD)

ATDD may come across as a combination of both TDD and BDD. However, the focus of this technique is on meeting the demands of users as against on getting the exact expected behaviour in the previous two techniques. This method is also called Story Test-driven Development (STDD).

The Acceptance Test-driven Development method gets together diverse stakeholders such as customers, developers, and testers. It is very important that all these stakeholders share common understanding of the user stories and their requirements in simple plain language which can be then transformed into programming language to write automated acceptance tests. For this, ATDD can draw upon BDD’s GWT approach.

Read more for TDD vs BDD vs ATDD

[mishastoesies]

if you make a problem where i end up going from deltaH(form) and deltaS(form) to deltaH(rxn) and deltaS(rxn) to deltaG(rxn) to deltaG(stdd) to Keq to [OH-] to pOH to pH you are NOT VALID

[boutbetties]

We love seeing derby rocks that teams hide out in their communities! It's such a fun and creative way to show the town your team is there and to maybe help get new fans! @sicktownderbydames . . . It’s that time!! We are rockin’ out again for our next bout 5/11! Find one of the all-blue rocks around town and get a Sick Town logo shirt (non-rainbow). Find one of the rocks (in the pic with 5 rocks) and get some STDD bucks to put toward some Sick merch! Stay tuned for clues!!! Let’s get it started!

[penandscythe]

Sooooo all I got from this week was that STDD’s (sexually transmitted demon disease) are now a thing.

[withacapitalp]

Masterlist/About Me

Since there's almost 300 of you now....how tf did that happen....anyway! I'm Liam here's all the stranger things fics I've written. I'll add my headcanons when I'm not feeling minority lazy lol Under a read more because I appreciate y'all's time lmaooo anyways!! Feel free to send me prompts and thoughts and general things because I love hearing from the people who follow me!!! If you just want to look for a tag it's under "Liam writes"

A New Perspective- Series primarily told from Wayne's perspective with him watching Steve interact with the kids and deciding the kid is actually not as bad as he thought. Steddie endgame

A Father By Any Other Name- Wayne Munson didn't hate Steve Harrington. He just really, really, really, didn't like him. A conversation he witnesses between Steve and Dustin might just start to change that though.

Scrapes, Sprains, and Headaches- When Lucas gets hurt learning how to skateboard, Wayne Munson gets another glimpse into how wrong he might be about Steve Harrington. He also is starting to see the beginnings of what might be a big big problem.

Just a Little Bit of Truth- Wayne goes to Steve's house, gets a little closer to the truth, and definitely needs to have a chat with his nephew.

Awkward Conversations- After his conversation with Jim, there's nothing Wayne wants more than to go home and finally talk with Eddie about everything that had happened. He decides to stay to the end of the party, which turns out to be both a frustrating and illuminating option. Featuring Murray Bauman being Murray Bauman, Steve being an angel of epic proportions, and Wayne and Eddie finally talking everything out.

Who Can Understand?- While everyone else goes to one of Eddie's shows, Wayne and Steve have a little talk.

Well I've Been Afraid of Changin'- Eddie likes Steve. Steve likes Eddie. It should be so simple at this point. But it's really, really, not. (CURRENTLY A WIP)

Days, Weeks, Months- Takes place immediately following S1 Steve's perspective on falling in love and dealing with the aftermath of whatever the fuck just happened. Stoncy Endgame

The Day After- The morning after Steve helps to destroy a demon who had been trying to kill Jonathan Byers and Nancy Wheeler, he goes to school. He didn't want to go. He didn't know why he did it. He just went. It was startling to see how the rest of the world didn't change.

The Weeks After- Steve loves Nancy. It's safe and it's good. It's normal. Steve knows he wants to spend the rest of his life with her. He knows he wants to buy her a house, wants to watch her age gracefully into the gorgeous woman he can see her becoming. Steve knows that he has an overwhelming urge to protect her, to keep Nancy safe from the very real danger they all know exists out in the world, even if she's usually the one protecting him. Steve just also wants all of that with Jonathan too. But that’s not inherently wrong. It doesn’t have to be. He wished he could believe that.

Stranger Things Daily Drabble- A daily prompt fill of just about anything Multiship like literally pretty much everything.

House and Home- Three weeks after getting kicked out of his parent's house, Eddie brings Steve to a decrepit house on the edge of Hawkins to show him how much he loves him Expanded from STDD prompt!

Empty/Full- Chrissy Cunningham is a Good Girl. She gets perfect grades, has the perfect boyfriend, and does exactly as she's told. She's doing everything she should, and she's utterly miserable. She just wants something to help her sleep. Just a little extra to get rid of all of the voices in her head and the pain in her stomach. Eddie Munson has a better plan. HELLCHEER

[blueb00tz]

I’m never gonna be able to finish that fucking stdd cover

[rynorlmo]

The same tree on a different day, but mostly sunset :) #PuertoRico #PuestaDeSol #STDD (at Building Beyond Me) https://www.instagram.com/p/CZo5vFSFdRr/?utm_medium=tumblr

[elenafisher]

When a cleric takes up an adventuring life, it is usually because his or her god demands it. Pursuing the goals of the gods often involves braving dangers beyond the walls of civilization, smiting evil or seeking holy relics in ancient tombs. Many clerics are also expected to protect their deities’ worshipers, which can mean fighting rampaging orcs, negotiating peace between warring nations, or sealing a portal that would allow a demon prince to enter the world. STRANGER THINGS / DUNGEONS & DRAGONS 
Will Byers ⚹ The Cleric

[victorfalade]

Unvaccinated Workers Won’t Be Allowed into Office from Jan. 17 - PS

Unvaccinated Workers Won’t Be Allowed into Office from Jan. 17 – PS

The FCTA Permanent Secretary, Mr. Olusade Adesola, issued the deadline in a circular dated January 10. The circular was addressed to the Executive Secretary of the Federal Capital Development Authority, all Mandate Secretaries, Coordinators of AMMC, STDD as well as Heads of all Departments and FCTA Agencies. Adesola said the directive was in line with the one issued earlier by the federal…

[ittechnicalandnontechnical]

TDD vs BDD vs ATDD — Developers’ Methodologies to Navigate Complex Development Processes Smoothly

Introduction

The last decade in the history of humanity can be easily called the technological revolution. The pandemic made it starker than ever before. The developers need to keep pace with the new languages, frameworks, tools, and processes that come into being every second.

To write code is a developer’s second nature. But, what code to write; how to write it; when to write it; and for what purpose may easily overwhelm even the most experienced and expert developers when it is raining new codes and processes day in and day out.

This constant flux can be easily navigated through the structured methodologies that focus on the task of the developers. Such methodologies anchor developers and their creations. Major development methodologies include TDD vs BDD vs ATDD, TDD stands for Test-driven Development , BDD stands for Behavior-driven Development (BDD), and ATDD stands for Acceptance Test-driven Development (ATDD).

Let us explore each in this post.

Test-driven Development (TDD)

Test-driven development method is about developing test cases before the developers start writing code. These test cases are essentially small units as per the requirements of the entire software.

The idea is to continually and consistently test the code against these test cases through the “red green refactor loop” until a stipulated unit is absolutely ready to be a part of the whole scheme.

One of the original authors of the Agile development manifesto, Robert C Martin has set forth three rules for TDD which are famously known as The Three Laws of TDD. They are:

1. You must write a failing test before you write any production code. 2. You must not write more of a test than is sufficient to fail, or fail to compile. 3. You must not write more production code than is sufficient to make the currently failing test pass.

The essence of these laws is to write the bare minimum code for the specific feature so that it passes the testing cycle successfully. The reason behind this exercise is to keep the codes clean and precise as much as possible at the unit level itself.

The best part of the TDD methodology is it allows the developers to experience the failure at the outset of the development. This helps them rule out all the possible flaws that may arise during the course of the development. And, that gets them the very exact code that is required for the exact expected software.

Major characteristics of TDD

Test-driven development promotes short development cycles for each unit to get finally added into the entire design of the software. Its major characteristics are:

Writing of the simplest and the shortest of the code possible that passes the unit test.

Restructuring the code that does not demand any alteration either in the functional or certain non-functional attributes of the entire software.

Advanced planning that often saves time during coding and debugging and brings about greater customer satisfaction and better performance.

Behavior-driven Development (BDD)

Behavior-driven development (BDD) is a higher version of TDD. This method tests if all the units of the application function as per the requirement of the entire application design.

In this extended version of TDD, a higher-level test which is often called functional test is created to rule out unnecessary code writing requirements for the maximum functionality of the application.

Having written the feature-failing test, the developers then test prototypes to obtain feedback on early failure and finally write the minimum code to get the correct application function at the maximum capacity. They keep writing this code until it passes the functional test.

GWT: BDD’s syntax

The acceptance test in BDD is created by defining the user story. All the developers, testers, QAs, experts, and product managers get together to review the requirements of each user story. They brainstorm and define a certain standard of each user story that has to be fulfilled.

The team uses Gherkin language to write the examples of user stories. The domain specific language Gherkin with its specific syntax exploits this approach of GWT which stands for Given-When-Then. They are:

Given: An actual scenario or the platform for the user to take the test, or username and password or entering of credentials by the user

When: The actual action that the user performs or pressing of the login button by the user

Then: The outcome of the action that the user performed in previous stage or sending the user to the home screen or the display of successful validation message.

Major Characteristics of BDD

Emphasis on defining user stories clearly so as to fulfill the requirements of each of them.

Reusability of the tests

Use of non-programming language to make the code accessible to all the stakeholders in the development process.

Focus on language and interactions.

Acceptance Test-driven Development (ATDD)

ATDD may come across as a combination of both TDD and BDD. However, the focus of this technique is on meeting the demands of users as against on getting the exact expected behaviour in the previous two techniques. This method is also called Story Test-driven Development (STDD).

The Acceptance Test-driven Development method gets together diverse stakeholders such as customers, developers, and testers. It is very important that all these stakeholders share common understanding of the user stories and their requirements in simple plain language which can be then transformed into programming language to write automated acceptance tests. For this, ATDD can draw upon BDD’s GWT approach.

Major characteristics of ATDD

Writing of user-centric acceptance tests

Improved communication and understanding between the teams in plain language

Improved code quality and specific tests in business domain terms

Facilitating quick feedback through failing tests

Reduction in time to market

Read More about the differences of TDD vs BDD vs ATDD

[revengereimagined]

We just released the ACT 2 theme on SoundCloud! Make sure to go check it out, it’s pretty awesome!