Software Engineering Goals: Delivering tasks and designing effective solutions

Here, so the next one of my goals is the third one on the list; there are eight goals in total, there are two sections of four goals each.

There is definitely a pattern emerging across the two, the more and more that I do this; I mean of course there was always a pattern there. 

But I am just spotting one more and more myself the deeper and deeper that I go into it. 

One of these patterns is translating human problems into code.

I love it. I love it. I just love it. I just love it. I just love it. I just love it. That's what it's all about isn't it? That's what we're here to do isn't it? Software engineering? Translate human problems into code.

Translating products into code.

Because you see products are really just all about solving problems. 

I know as much. I worked in product once.

I did pretty well at it. I just couldn't stay in it for long.

I loved coding too much, you see.

Anyway, I digress.

Let's go further into the goal. But translating human problems, or a feature request, into code, into tech, into software, is a big part of it, you see.

So what is goal 3 all about then? thanks.

Goal number three is about delivering tasks and designing effective solutions to product features and small scope engineering challenges.

Imagine me saying to myself this, please: 

"This is the feature; I need to do all of these different bits and pieces." So it is about designing that solution and at a very simple level and scale the software and architecture of it. It's about identifying what parts of the system need to change in order to fulfil the feature request. Basically I just think of it all as:

• "Here's the problem
• I get the problem
• I am going to design step by step what I am going to do with this problem
• Before I actually implement the task (this is goal 4!!!), and deliver it step by step, let me actually design what the solution is, please, thank you."

And ultimately it is about BREAKING UP THAT HUMAN REQUEST INTO WHAT NEEDS TO HAPPEN IN THE CODE.

BREAKING UP THAT HUMAN REQUEST INTO WHAT NEEDS TO HAPPEN IN THE CODE.

BREAKING UP THAT HUMAN REQUEST INTO WHAT NEEDS TO HAPPEN IN THE CODE.

But if you really think about the feature then it's about the first step of the process, from receiving a feature request, to delivering a working feature.

So if you think about it: the feature comes in -> I design a solution -> I deliver that solution -> the feature is done.

So this is really the first part of that process.

"I design a solution." I love it. I love it. I love it. Love it. Love it. Thank you. Thank you. Thank you. Thank you. Thank you. Love it all. Love this process. 

Thank you. I love this whole journey, thank you. Thank you. Wow.

Btw, I have been listening to Mallrat again, one of my favourite artists.

I mean, she really just reminds me what it is to care.

I mean just, WOW. And I do all of this because I care.

I mean, just, WOW.

P.S. I forgot to add this in but I shouldn't need to be told to add in a test. I should be able to know this and figure out what needs to be tested. I should be able to think: what needs to be added/changed here that might need to be tested? Thanks!!!! 💚💜💙