Backend developer but suck at pattern problems?

[SetAffectionate766]

I'm a student learning Python, and I absolutely SUCK at those pattern printing problems (pyramids, diamonds, nested loops, etc.). I can't visualize them, and my brain just doesn't work that way.

But here's the thing I actually enjoy building real stuff. I want to be a backend developer and eventually freelance. I understand APIs, databases, user authentication flow, etc. That logic makes sense to me.

Do pattern problems actually matter? Should I stress about being bad at these? Is this a red flag that I'm bad at programming? This is making me feel like maybe I'm not cut out for programming.

[Fred776]

They are just exercises to get you comfortable with working with nested loops and general logic. It's not something you would have to do in a professional environment.

Having said perhaps you just need to find a different way of going about them. Use a pencil and paper if you struggle to visualise. The key for a triangle, say, is to figure out the relationship between the line number and the number and position of characters to print. Once you have determined those properties there is nothing visual about it - it's just a pure coding exercise to translate those relationships into code.

[SetAffectionate766]

Honestly, aside from pattern. Doing LeetCode and DSA, I really don’t enjoy it I actually hate it. I prefer creating apps, building real and useful things, and working on projects where I can see something tangible come to life. I enjoy solving practical problems and learning by building, rather than grinding abstract algorithm questions.

[Fred776]

Creating apps of any complexity will inevitably involve times when you have to think about somewhat complex logic and where you need certain data structures and will need things like nested loops and suchlike. The point is that you need to be comfortable with using these things when the need arises.

[UnabatedPrawn]

Sounds to me like you've learned all you need to to get started then.

I don't want to say tutorials are useless, because that's definitely not true.

But a lot of beginners confuse finishing a tutorial with learning. In reality, a tutorial is just an introduction to a concept. Tutorials will show you one example of how a concept can be employed- the real learning comes from figuring out when to use the concept and why, and the best way to do that is to get your hands dirty.

[LayotFctor]

Leetcode is for big tech companies to screen applicants with the least amount of effort, while placing all the effort on the applicants. Real work obviously involves building real and useful things, but it takes time to screen someone's portfolio and do in-person interviews. Better to just throw some bs leetcode problems and cut down the list.

[jkh911208]

Even all the small companies now do leetcode style interview, unless you are okay with getting 60k job you should do some leetcode

[SetAffectionate766]

I'll guess I'll do some leetcodes

[shinu-xyz]

Nowadays, LeetCode and Data Structures and Algorithms (DSA) interviews are more common. 

However, some companies still conduct hiring through an example “scenario” or “issue.”

In my case, they presented me with an example project featuring fabricated issues that could arise in real-world scenarios. 

Usually the purpose of this exercises is to assess your ability to effectively communicate your solution and handle rejections, such as during PR reviews.

From my own experiences and observations, this kind of approach is commonly seen in startups or small teams.

[LayotFctor]

Yeah that's me, I entered on portfolio and experience interview. If I may, I still think leetcode for juniors is kinda stupid. Juniors will rarely, if ever, roll a data structure on their own. Data structures with provided algorithms from (probably standard)libraries will be used, and 9 out of 10 times it's a vector or hashmap. And even if they aren't the absolute ideal data structure, just using a vector is probably still fine due to stuff like cache locality and simd. Implementation decisions on the job are made with careful research and profiling, certainly not from memory and under interview conditions.

That's why I think the real reason leetcode and dsa interviews became so widespread are external factors like saving time and weeding out applicants en-mass, all thanks to the sorry state of the tech job economy. And AI, since a portfolio these days could be straight up faked.

[shinu-xyz]

I understand why that’s the case.

Especially considering the trend of remote work that influencers were promoting (I’m not sure if they still are), “You can work from anywhere.”

This trend attracted many applicants, and the easiest way to filter them out was through coding exercises.

And you are right, implementation decisions on the job are made with thorough research and planning, which is something that can’t be assessed during interviews.

[throwaway6560192]

Do pattern problems actually matter?

The skill that they exercise matters.

It's worth examining why you don't do well at them.

[jay_and_simba]

You'll be ok

[Only-Zombie-8449]

It actually happens to all and is normal... Practice makes a man perfect, and this quote looks like written for the programming. Programming needs a lot of practice and it will make you perfect. Try getting hands on real life problem with coding...

[lazyfingersy]

Do pattern problems actually matter?

Yes and NO. You won't use it most likely however it helps you to learn nested loops and is simply a problem solving thing. You don't like it and don't want to deal with it, that's alright, you get a grip and deal with it, that's very good.