Oooo, Jake and Zeke in the same room, and there's only room for one in Abigail's thoughts. Most interesting indeed... >.>
Great chapter!
z
Warning: This work has been rated 18+ for language and mature content.
In the following weeks, computers became an extension of my being. Like when I methodically layered colors onto a canvas, I constructed the intricate landscape of my project. I fine-tuned every detail, designing the user interface with content that weaved entrepreneurship into artistry. Each line of code was a deliberately written algorithm combined to create.
In the Innovation Hub, Professor Coleman’s explanations were patient and enlightening. He unraveled the complex concepts of coding thread by thread. His encouragement to perceive algorithms as an art form helped me understand when I grew frustrated. With that association, I saw the artistry in programming logic.
Like the rest of the Innovation Hub, the computer lab exuded a modern, minimalist vibe. Rows of sleek, ergonomic tables stretched across a spacious room, each adorned with two innovative computers. These stations encouraged collaboration or multi-tasking. Lights cast in circular orbs hung at different lengths from the ceiling and created a calm while the hum of the powerful machines sang promises of limitless digital potential. One afternoon, Professor Coleman and I were deciphering a complex code section when Zeke entered the computer lab.
The screens made a blue shadow fall on my face as I froze, staring at him. He walked, backpack slung over one shoulder, to a station a few rows ahead of us. His hoodie covered his face, but I only needed to glimpse his neck to know it was him. He took his hood off, and I noticed headphones in his ears. I wondered what music he was listening to. I berated myself for staring and having any care or interest in him.
Professor Coleman, noticing my momentary distraction, followed my gaze and met my eyes with a knowing smile.
“Ah, young love,” he uttered to himself.
When I got caught, my cheeks grew hot, and I felt like someone had exposed my internal world. I hastily returned our attention to the screen, asking about what we had been working on.
We bounced back to the trenches of tweaking and fixing what was not working correctly. Yet, despite my returned fervor, anxiety simmered deep inside me, a hidden undertow threatening to overtake me. Learning the cryptic language of code under Professor Coleman’s guidance was like deciphering an ancient script.
When I painted, my work was immediately visible, but each line of coding–a blur of numbers, text, and symbols–had to be debugged and fine-tooth combed. My patience and frustration caused me to need breaks.
Jake’s support kept me grounded and motivated, beyond my laptop screen. He popped in shortly after Professor Coleman left, and I had another moment of frustration. As he entered the lab, his presence reminded me that the world continued to spin outside the realm of my project.
He walked down the middle aisle, passing Zeke on his way. My work area was in disarray. Computer and programming textbooks were open around the table. As he approached, I removed my headphones and smiled at him.
With a grin, he playfully called out, "Hello, coding wizard," offering a cup of coffee as a peace offering.
I laughed awkwardly, gesturing for him to sit next to me. “Hey, yourself. Thanks for the caffeine boost.”
He sat, studying my setup and looking over my screens.
“So, how’s it shaping up?” He handed me the coffee, and I gratefully took a drink.
I launched into a spirited rundown of my triumphs and hurdles. He was attentive, asked questions, and showed interest in my progress. The irony did not escape me, though. Jake was so kind while I was thinking about Zeke, drawn to him like celestial bodies pulled by an invisible force. While Jake offered predictability and loyalty, something behind Zeke’s aloofness had me interested. A familiar guilt nagged at the edges of my consciousness. I forced myself not to look in Zeke’s direction as, in my peripheral, I saw him pack up and leave.
A few days later, a rainstorm pounded on my dorm building. I had been dodging Jake’s calls, and the guilt grew like a tsunami. His texts became more concerned, asking what he did wrong, which was nothing, but I could not tell him what was happening.
So, I invited him over. I worked at my desk while he studied on my bed, lying on his stomach. Hours went by with us barely speaking. The silence between us intensified until it became deafening. Finally, he put his book down, sat up, and cleared his throat. I looked over from my computer screen but said nothing, quickly returning to my work.
“Is everything okay?”
I let out an exasperated sigh, feeling frustrated both with myself and with his question. I swallowed and tried to come up with a reasonable excuse. “It’s…well…it’s this project. It’s taking up so much of my time. Sorry.”
He crossed the room to stand behind me, touching my shoulder. “You don’t have to apologize. I understand this means a lot.”
My smile to him held both gratitude for his understanding and a deepening sense of guilt for my lies. “It really does.”
He leaned down and kissed the top of my head. “Well, I’ll be around if you need me for anything. I love you.” With that, he left.In the following weeks, our interactions dwindled to non-existent. I continued to use my project as an excuse, a shield to push off addressing the growing distance between us. My focus became singular, my tunnel vision solely on the project’s development. I told myself I would make it up to him once this was over, but deep down, I knew that was also a lie.
Oooo, Jake and Zeke in the same room, and there's only room for one in Abigail's thoughts. Most interesting indeed... >.>
Great chapter!
Hi it's 22Midnight again
hope your doing well, let's get into it!
First Impression: Laptops are being brought more into the story and we might be going into politics maybe I'm wrong but laptops mean sometimes lots of politics whatever this is about her art probably and hopefully more Zeke, and the mysteries person was she his ex or something don't know will have to see won't we.
In the following weeks, computers became an extension of my being. Like when I methodically layered colors onto a canvas, I constructed the intricate landscape of my project. I fine-tuned every detail, designing the user interface with content that weaved entrepreneurship into artistry. Each line of code was a deliberately written algorithm combined to create.
In the Innovation Hub, Professor Coleman’s explanations were patient and enlightening. He unraveled the complex concepts of coding thread by thread. His encouragement to perceive algorithms as an art form helped me understand when I grew frustrated. With that association, I saw the artistry in programming logic.
Like the rest of the Innovation Hub, the computer lab exuded a modern, minimalist vibe. Rows of sleek, ergonomic tables stretched across a spacious room, each adorned with two innovative computers. These stations encouraged collaboration or multi-tasking. Lights cast in circular orbs hung at different lengths from the ceiling and created a calm while the hum of the powerful machines sang promises of limitless digital potential. One afternoon, Professor Coleman and I were deciphering a complex code section when Zeke entered the computer lab.
The screens made a blue shadow fall on my face as I froze, staring at him. He walked, backpack slung over one shoulder, to a station a few rows ahead of us. His hoodie covered his face, but I only needed to glimpse his neck to know it was him. He took his hood off, and I noticed headphones in his ears. I wondered what music he was listening to. I berated myself for staring and having any care or interest in him.
Professor Coleman, noticing my momentary distraction, followed my gaze and met my eyes with a knowing smile.
“Ah, young love,” he uttered to himself.
When I got caught, my cheeks grew hot, and I felt like someone had exposed my internal world. I hastily returned our attention to the screen, asking about what we had been working on.
We bounced back to the trenches of tweaking and fixing what was not working correctly. Yet, despite my returned fervor, anxiety simmered deep inside me, a hidden undertow threatening to overtake me. Learning the cryptic language of code under Professor Coleman’s guidance was like deciphering an ancient script.
When I painted, my work was immediately visible, but each line of coding–a blur of numbers, text, and symbols–had to be debugged and fine-tooth combed. My patience and frustration caused me to need breaks.
Jake’s support kept me grounded and motivated, beyond my laptop screen. He popped in shortly after Professor Coleman left, and I had another moment of frustration. As he entered the lab, his presence reminded me that the world continued to spin outside the realm of my project.
He walked down the middle aisle, passing Zeke on his way. My work area was in disarray. Computer and programming textbooks were open around the table. As he approached, I removed my headphones and smiled at him.
With a grin, he playfully called out, "Hello, coding wizard," offering a cup of coffee as a peace offering.
I laughed awkwardly, gesturing for him to sit next to me. “Hey, yourself. Thanks for the caffeine boost.”
He sat, studying my setup and looking over my screens.
“So, how’s it shaping up?” He handed me the coffee, and I gratefully took a drink.
I launched into a spirited rundown of my triumphs and hurdles. He was attentive, asked questions, and showed interest in my progress. The irony did not escape me, though. Jake was so kind while I was thinking about Zeke, drawn to him like celestial bodies pulled by an invisible force. While Jake offered predictability and loyalty, something behind Zeke’s aloofness had me interested. A familiar guilt nagged at the edges of my consciousness. I forced myself not to look in Zeke’s direction as, in my peripheral, I saw him pack up and leave.
A few days later, a rainstorm pounded on my dorm building. I had been dodging Jake’s calls, and the guilt grew like a tsunami. His texts became more concerned, asking what he did wrong, which was nothing, but I could not tell him what was happening.
So, I invited him over. I worked at my desk while he studied on my bed, lying on his stomach. Hours went by with us barely speaking. The silence between us intensified until it became deafening. Finally, he put his book down, sat up, and cleared his throat. I looked over from my computer screen but said nothing, quickly returning to my work.
“Is everything okay?”
I let out an exasperated sigh, feeling frustrated both with myself and with his question. I swallowed and tried to come up with a reasonable excuse. “It’s…well…it’s this project. It’s taking up so much of my time. Sorry.”
He crossed the room to stand behind me, touching my shoulder. “You don’t have to apologize. I understand this means a lot.”
My smile to him held both gratitude for his understanding and a deepening sense of guilt for my lies. “It really does.”
He leaned down and kissed the top of my head. “Well, I’ll be around if you need me for anything. I love you.” With that, he left.In the following weeks, our interactions dwindled to non-existent. I continued to use my project as an excuse, a shield to push off addressing the growing distance between us. My focus became singular, my tunnel vision solely on the project’s development. I told myself I would make it up to him once this was over, but deep down, I knew that was also a lie.
Hello friend!
It's me, back again, for another chapter!
Per my interpretation, this was a great addition to this novel that gave a lot of interesting insight into Zeke and Abigail's relationship!
Abigail is working in the computer lab when Zeke walks in, but they both do their best to ignore one another. Some time passes, and Abigail invites Jake over, and they hang out. While they're talking, Abigail says that her project has been taking up so much of her time that she can't focus on their relationship as much, and this is also the excuse she uses to see Jake less and less.
This was a really interesting chapter!
If I could offer any sort of advice, I wouldn't! I didn't notice anything wrong grammatically or structurally, and I thought you did a great job!
If I had to pick my favorite part, it would definitely be the part where Abigail was explaining her frustration with coding and programming. It showed a lot about how her mind works and the way she processes certain things in a really fascinating way! You said,
When I painted, my work was immediately visible, but each line of coding–a blur of numbers, text, and symbols–had to be debugged and fine-tooth combed.
Points: 84229
Reviews: 407
Donate