#the coder

[cyan-stargaze002]

What if The Coder was in the TF2 Comics?

I tried to copy the style with my own + the coloring as well. It was really fun to do this. I will make a proper reference of her later on.

📱👾

[helloworldscripter-here]

Good question, why am I going on anon?🤔🤔

I think I'm a dumb dumb

thou hast no need to hide yourself for I know who thou are...////

[helloworldscripter-here]

Just don't die with the drafts! Take breaks and water! Andd uhhhhh pokemon

– Itrapped again I don't wanna write the whole name-

I never played or watched pokemon guys I'm uncultured 💔💔 but yes I will trust... I just wanna finish it this time bcuz its school break rn///

Speaking of which why are you going on anon//

[helloworldscripter-here]

You alive?🥺

– Itrappedwithdarkheart

YEAH I AM I SWEAR I JUST FEEL UNMOTIVATED RN BCUZ I NEED TO FINISH LIKE 4 ART DRAFS BUT I PROMISE ILL GET TO YOU SOON💔💔💔💔💔💔////////////

[helloworldscripter-here]

Some basic Lore to get some of you all integrated. of course not everything. ^_^

Scripter uses they/it/he.

They're aroace but likes the prospect of having a relationship( Cupioromantic ).

Scripter does NOT have a physical form. Anytime one talks to them, it's either holographic or through a screen which may or may not be visual. This technically means that one CANNOT hurt him unless they manage to control the foundation of the code he was built upon. Oof.

--- > However, they can hurt someone by hacking them, which in my AU is the equivalent of mind control / body occupation. PROVIDED they have code to hack in the first place.

Scripter talks through text and uses a screen or panel to do so. He does not have a voice unless he uses soundbites or text-to-speech.

Scripter is physically a young adult but is much, much older.

Scripter is not and never was a full fledged admin, though may have been considered one socially due to lore reasons.

Their mood changed a TON, and often has dizzy spells or spells of sadness at random intervals. There is no way to help them out of this state, so it's better to just ignore it.

Most notable information through asks( so someone doesn't have to scroll endlessly. ):

-Builderman is the only admin who visits them. -Roblox is the one that trapped Scripter.

[cloversion]

IT'S YOUR BIRTHDAY, ISN'T IT. HAP BIRTH YOU WONDERFUL YOU

thank you all!!@goodbro: that's my secret, bro. im always alter ego.

[je18573-blog]

Chapter 7

『輸入若是垃圾，輸出也會是垃圾。』

客戶對功能的設想，其實經不起在電腦前真刀實槍的考驗。

『完成』意味著所有程式碼都寫完了，所有測試都通過了，QA和需求方已經認可。

測試是為了確定系統的各項指標符合要求。

絕不能被動接受測試！

職責是協助團隊開發出最棒的軟體。

=================================

【過早精細化】 業務方未啟動專案，就精確要知道最後能得到什麼；開發方尚未評估整個專案，就希望精確知道要交付什麼。

－東西畫在紙上與真正做出來，是不一樣的。

－ 不確定原則(或稱觀察者效應)： 每次向業務方展示一項功能，他們將獲得更多資訊，而這些新資訊進而影響他們對整個系統的看法。

－需求完成得越精確，就越容易被忽視。

－即便擁有全面精確的資訊，評估也通常存在巨大變數。

－需求是一定會變化的，所以追求那種精確性是白作工的。

【遲來的模糊性】 為避免過早精細化，就盡可能地『推遲』 精細化。專業開發人員直到開發前一刻才將需求具體化，結果可能反而造成另一問題『遲來的模糊化』。

=================================

業務分析員：測試『正常路徑』，以證明功能的業務價值。

QA：測試『錯誤路徑』、邊界條件、異常、例外情況，考慮哪些部分可能會出問題。

=================================

驗收測試 != 單元測試

單元測試： １程式設計師to程式設計師 ２正式的設計文件，描述底層結構&程式碼行為。 ３關心者為程式設計師。 ４深入系統內部執行，呼叫特定類別的方法。

驗收測試： １業務方to業務方 ２正式的需求文件，描述業務方認為系統應如何運行。 ３關心者為業務方&程式設計師。 ４在系統外部，通常是在API或UI層級進行。

這兩者首重的是『文件』，然後才是測試。 它們的主要目的是以文件如實描述系統的設計、結構、行為。

=================================