Beautiful! Brb, showing these pictures to my wayetti as inspiration 🤣

I second this, and would generally recommend finding some people to talk to who are in jobs similar to those you are considering, even if you aren’t able to shadow them. And you don’t have to be in university to do this–ask people you know if they know anyone in jobs or careers related to those you are considering, and ask to pick those people’s brains. Ask them about what they like and dislike about their current job, what previous jobs/positions they’ve had and what they learned from those roles, what decisions they made that shaped their career path, what advice they would give to someone curious about or just starting in their field, etc.

I’ve found that people who are passionate about their jobs/careers often love to talk about how they got to where they are and what they wish they had known earlier along their career journey. Heck, most people enjoy talking about themselves in general, so don’t be shy! I did this with a couple of friends’ parents when I was trying to decide what to major in in college/university, and more informally along my early career trajectory with others I met, and it has been a huge help. One of the people I talked to even helped me realize how flexible a degree program I was considering could be, and she was absolutely right! And who knows–you may even meet someone who turns out to be a great mentor.

Picking a career path is intimidating, but it’s a path, not a label you’re stuck with the rest of your life! Even if you take a job that isn’t a good fit for you, it can teach you more about your strengths/weaknesses and what growth areas interest you. When you come to a fork in the road of your career path–you learn about a promotion opportunity, see a job posting at another company, or even just have a conversation with your manager at your current job–you’ll have the opportunity to make decisions that could help you find a role that’s a better fit for you (or even re-shape your existing role to fit your strengths and passions better). Learning about other people’s careers–especially the choices they made and what came of them–can be a huge help as you walk down your own career path.

Best wishes for your journey! It’s completely normal to be uncertain in making big career decisions, but you got this!

(EDIT: minor rephrase)

In the USA and other English-speaking countries: weary =/= wary.

For example, I’ll see someone write something like: “I am weary of the campfire because it is so hot”

You aren’t tired of the campfire! You are wary of it!

I’m glad you found it helpful! And no, I love my current job, but I appreciate the sentiment!

To add onto this, sometimes it’s about getting more specific with your questions to get the more specific answers.

For context of how I would suggest structuring these detail questions, here’s how I think about code I write or debug: The functions and classes my code is made of are meant to get specific inputs to become specific outputs via a defined process; I think of this as inputs->how->outputs. Figuring out what inputs you need to execute the “how” part to get the outputs you want is the puzzle of each function or class I write. The “how” part can even be broken down further into smaller chunks of inputs->how->outputs.

I think asking your engineer friends to frame things in this context would both show your appreciation for the nitty-gritty details you are needing, as well as give you further context to ask more detailed drill-down questions (about deeper levels of inputs->how-> outputs) if needed. For example: “you said to get inputs A and B to result in output C, we need to run the fizzbuzz algorithm on A and B. What roles do those inputs have in that algo? Do we have to do any preprocessing on A or B before we fizzbuzz them, or any post processing of the fizzbuzz’s direct output to get C?” “Oh, yeah, we have a wrapper that takes A and makes it column-major so that fizzbuzz executes faster, but we need output C to be row-major for when it goes into otherFunction(), so we do such-and-such to fizzbuzz’s output to get the C we output.” This gets you a level of detail deeper, and you could ask further questions about the transformations happening to A and the post-processing of fizzbuzz output to get C, as well as get more context for otherFunction to ask more about later.

You could also use this context to ask further questions about what they think the future implementation should look like. “Are there any assumptions we can make about A and B or how C is used that could simplify how we go from the former to the latter? Are there any requirements on the inputs and outputs that would better be either relaxed or made more stringent, and if so, in what way?”

I hope that helps! Best wishes for your work on this project–streamlining processes is hard, especially when working with other people’s code, but your appreciation for the details to get things implemented well is admirable!

The oddest I’ve ever encountered: EXACTLY 15 characters long. No more, no fewer. 15.

Honorable mention: Various online accounts where I used my password manager to generate a long, secure password, which the website accepted without warning or error. I was then locked out because their user management system could not handle such long passwords (had to create a second account with a much shorter password to find that out) 🤣

This is a great analogy! To build on these points and the analogy: I like to think of my coding in terms of inputs, outputs, and what needs to happen to the inputs to get the outputs I want: that is, inputs->how->outputs. So for this buttered toast analogy, your inputs would be:

• toaster
• electricity
• bread
• butter
• knife
• plate
• operator’s hands

The desired output: toasted bread on the plate with butter spread on one side.

The “how” is the sequence of specific instructions the instructor gives to the operator.

This approach is even more helpful as you start working on larger projects; as you think about a problem you’re trying to solve, try to break the overall input->how->output into smaller modules of input->how->output, and then you can use those modules (often called “functions” or “methods”) in the overall “how.” Let’s say you want the instructor and operator to prepare a full breakfast with bacon, eggs, and buttered toast. You’ll have some more inputs, of course (frying pan, raw bacon, shelled eggs, stove, in addition to the toast components), but since you already made a known-good make_buttered_toast function, you can incorporate that function into the pipeline to go from your more comprehensive set of inputs to the full breakfast outputs, and you can make separate functions for making the bacon and making the eggs. Finally, your overall program can then call your bacon, eggs, and toast functions to result in the desired output of a full breakfast.

Now here’s where breaking the problem down into smaller input->how->output chunks really comes in handy: one day, you are tweaking your breakfast-making code, and suddenly, your overall outputs have good bacon and good toast, but the eggs wind up dumped half-cooked on the stove. But since you made nice, modularized functions for toast, bacon, and eggs, you automatically know more where to start looking for the bug: the eggs function.

There’s a lot of good advice in the responses to this post! Overall, I just wanted to emphasize what I wish I had learned much earlier on in my career: the benefits of thinking in terms of inputs->how->outputs and modularizing sub-problems in the overall program’s “how” into subproblems that can be independently considered, debugged, and re-used on future projects. (A secret for you: those of us who have been coding for a while often don’t start everything from scratch–we’ll re-use some functions or classes we wrote in the past, tweaking them as necessary for new applications, but not needing to start from a blank text editor :) ) Learning to write applications in code is exploring a new way of thinking about problems and how to solve them, and personally, I find it very rewarding!

I wish you all the best on your coding journey!

Yes! Another fan of spicy sausage in stuffing! My mom one year made the stuffing (not cornbread-based–Stove Top brand with savory herbs, I think) with half mild sausage and half spicy sausage for younger me who didn’t like much spice. We also added pecans and dried cranberries in addition to onion and celery. We’ve barely ever deviated from that recipe since!

Even better: purchase an inexpensive strap wrench with a rubber strap (something like this) and keep it in the kitchen for stubborn jar lids. For the jar lids that even a strap wrench alone can’t quite open, I’ve had success by using the strap wrench on the lid while holding the jar itself with a silicone oven mitt (or oven mitt with rubberized grip–the rubber band trick might work here as well).

Another non-minty toothpaste: Tanner’s Tasty Paste (here’s an amazon link for their Vanilla Bling flavor, which is indeed tasty: https://a.co/d/eyJlgCk). It’s apparently intended for kids, but it has the same active ingredient as regular fluoride adult toothpaste!

Having worked for people who (even if they didn’t do so intentionally) treated me differently after I told them I had ADHD, with my current job, I’m seeing how things go not disclosing my ADHD to my manager or coworkers explicitly, but mentioning what is a weakness or strength for me. This is in a work culture where the managers are managing a bunch of researchers (aka nerdy specialists 🙃), and so it is accepted that not everyone will be good at everything, and that’s ok–we can choose what of our strengths we want to build on more, choose what of our weaknesses we want to work towards growing in, and choose what weaknesses we are willing to let stay a weakness (and ask someone else to do–fortunately it’s a large workplace). So I’ve approached this by telling my manager or coworkers that I am, say, not great at estimating how long a given task will take, or telling them that I am great at organizing projects that I find especially compelling (and not as great at organizing things that I don’t find as interesting), or that sometimes I’ll bounce back and forth between tasks but I can still get things done. So far, that has been received pretty well. It’s not that I want to assume that my coworkers and manager will treat me differently if I tell them I have ADHD–I don’t know whether they have pre-conceived notions about ADHD, and if I tell them explicitly, it’s a bell I can’t un-ring. But it’s absolutely a personal choice about who to tell, under what circumstances, and how to present the info. Best wishes in whatever you decide to do! ❤️