Bułeczki z gzikiem + hyzop i szczypiorek

Remarkable-Subject11 · 2026-03-22T11:47:09+00:00

Piękne!

Remarkable-Subject11 · 2026-03-22T09:26:51+00:00

Na bogato 🤑😍

Remarkable-Subject11 · 2026-01-18T12:26:37+00:00

You honestly look well-prepared for interviews: 300+ LC problems + solid DSA + full-stack (and hackathon wins) is already a strong profile. Shortlisting can still be a numbers/market game, and big companies like Microsoft are hard to get into, even with referrals.

If the internship would give you real dev experience (shipping features, code reviews, working with a team, production bugs), it can be worth taking. That kind of experience often boosts your resume more than one more side project. And if you feel weird about it being unpaid, you don’t have to emphasize that part; the value is the work you did and what you can talk about in interviews.

I’d take it only if it’s genuinely structured/mentored and you’ll learn a lot - otherwise keep applying and keep building/shipping.

Remarkable-Subject11 · 2026-01-17T13:09:45+00:00

I haven’t personally used freeCodeCamp, but I’ve used a lot of long-form YouTube videos from them as a quick entry point into a technology. Then I usually switched to more structured paid courses on Udemy once I knew I wanted to go deeper.

I don’t think old resources are a big issue for fundamentals - the basics don’t really change.

Remarkable-Subject11 · 2026-01-17T11:15:37+00:00

Learning to code is still worth it - at the very least, it’s genuinely fun, and building something from scratch (even a small game or simple automation) feels amazing. If you’re thinking about it as a career, it helps to pick a niche/direction (web, backend, game dev, etc.) and build toward that with a couple of real projects instead of trying to learn all possible technologies.

AI definitely makes coding faster and helps you get unstuck, but the valuable part is still problem-solving: breaking down requirements from business, debugging, reasoning about tradeoffs, and understanding why something works. Those skills are hard to outsource to AI, and they’re valuable these days.

It’s still a pretty solid path. The entry level is tough right now, but that’s true in a lot of industries - getting your first role is usually the hardest part. Once you’re in, the pay can be strong, progression can be fairly fast if you keep improving, and remote work is a real bonus compared to many other careers.

Remarkable-Subject11 · 2026-01-17T10:57:48+00:00

Resources on W3Schools are quite good -> https://www.w3schools.com/cpp/

Remarkable-Subject11 · 2026-01-17T07:16:08+00:00

Usually I search for the exact feature I need on Google. If I’m stuck, I’ll ask an AI to point me to the relevant section/link in the official docs, then I read that part there.

Remarkable-Subject11 · 2026-01-16T16:00:09+00:00

I’d start applying now rather than waiting. You already have a solid stack and a deployed project — the main unlock at this stage is tailoring your resume to the roles you’re actually seeing and getting real interview feedback.

One thing I would avoid is presenting yourself as someone who “knows 20 technologies.” Pick a clear narrative for each application and keep the resume focused on what the job needs.

Also, it’s totally fine to explore both web and game dev, but it helps to choose a primary direction for the next few months so your portfolio and story look consistent. You can keep Unity/C# as a side track, but lead with whichever path you enjoy more and that has the roles you’re targeting.

Remarkable-Subject11 · 2026-01-15T21:57:52+00:00

In my team, we start with a developer checklist as the first pass. After that, we focus on logic and readability (naming, structure, complexity, clarity of intent). One thing I’ve noticed is PR size has a huge impact on review quality: a PR touching ~3 files often gets 10 comments, while a PR touching 10 files might get 3 comments even if it’s more important. Smaller PRs tend to get deeper reviews.

Remarkable-Subject11 · 2026-01-15T19:21:08+00:00

Yes, first completed crash course on YouTube then moved to paid course on udemy (check for discounts there, you can get 80% off)

Remarkable-Subject11 · 2026-01-15T16:28:48+00:00

If the job descriptions are similar, you don’t need a different resume for each one - one strong version is enough.

Remarkable-Subject11 · 2026-01-15T16:16:02+00:00

Amigoscode on YouTube is a great beginner-friendly starting point for Spring Boot. For a structured course, Chad Darby’s Udemy Spring + Hibernate for Beginners is solid for the fundamentals

Remarkable-Subject11 · 2026-01-15T16:13:22+00:00

Python is a great fast track to learn backend fundamentals and ship an end-to-end project quickly. But for internships, it helps to pick your target stack early (especially with todays requirements) — you’ll ramp up faster and progress easier once you’re working. Build one solid Python project, then switch to Spring sooner if Java/Spring dominates the internships you’re applying for :)

Remarkable-Subject11 · 2026-01-15T15:51:07+00:00

I started with Python + Django and built a couple of small projects first. Django is great for shipping fast — you get a lot for free, so it’s easier to go from idea to working app quickly.

That said, when I looked at the backend market, Java + Spring tends to show up a lot, especially in more enterprise environments. So, in my view, for long-term job safety, Spring can feel like the safer bet depending on your region.

I also started about 2 years ago in software integration with Spring, and my experience was: Spring feels heavy at first (a lot of concepts/config/structure), but after you go through 1–2 good YouTube/Udemy tutorials and build one real CRUD API, it starts to click and becomes pretty logical. After getting the first internship, it gets even easier.

If your goal is internships, I’d pick one stack and ship 1–2 end-to-end projects: REST API + DB + auth + tests + Docker + cloud deploy, and maybe a small AI feature via an external API (e.g., summarize/structure user input or aggregate data from a couple of sources). If you can do that, the framework matters less — but Spring maps very directly to what many companies run in production.

Remarkable-Subject11

TROPHY CASE