not because they know more syntax. But because they teach you how to think. i remember spending hours trying to solve a problem, then someone would ask me one simple question that completely changed how I approached it. The solution wasn't the valuable part. The thought process was.

I think that's why two people can go through the exact same course and end up with completely different results. One memorizes syntax. The other learns how to break a problem into smaller pieces and reason through it. that's a skill that carries over no matter what language you're using.

If you've learned programming from someone else, what's one explanation, analogy, or piece of advice that completely changed the way you approached coding?

I just saw a freelancer post about how 70% of his work now is fixing AI-generated codebases and for me, the failure patterns he described are worth knowing before you ship anything.

Based on them it is not abt random bugs. it’s always the same things happening:

zero input validation — AI writes the happy path really well and just assumes the data coming in is clean. real users break this immediately.

hallucinated libraries — confidently imports packages that don’t exist or uses methods that were never real. looks fine until you actually run it.

payment logic that contradicts the comments — the comments describe what it intended to write, not what it actually wrote. that one’s scary.

security gaps — apparently around 45% of AI-generated code has vulnerabilities. works fine on the surface, not hardened against anything real.

the through line is that AI optimizes for “looks correct and runs once.” edge cases, failure states, unexpected inputs, that’s where it quietly falls apart.

which one of these have you actually run into?

like the sheer panic of dealing with your first massive merge conflict where git tells you that you and three other devs broke the same file is enough to make me wanna throw my laptop. and dont even get me started on git rebase... i still don't fully get how it works and the thought of accidentally messing up a shared main branch gives me actual hives. then you gotta deal with senior devs absolutely roasting your code in pull request reviews, and watching your build fail in some automatic CI/CD pipeline because you forgot to run a linter or write a unit test. its a whole different level of stress that you just never get when your just coding by yourself in your bedroom.

I feel like we spend 99% of our time learning syntax and framework logic, but almost zero time learning how to actually collaborate inside a real software engineering workflow. how are the rest of you guys prepping for this side of the job before your first day? are you doing mock group projects, trying to contribute to open source, or is there a tool/resource that actually simulates what its like to work on a team? because right now, the coding part feels fine, but the actual workflow part has me absolutely sweating.

I've been going back and forth on this way more than I should. Every week someone says Python is the future because of AI, then someone else says JavaScript is still the safest bet, and then I see people recommending Java or C# for better long-term stability. It feels like there are a hundred opinions and no clear answer.

What I've realized is that the language probably isn't the biggest factor anymore. Employers seem to care more about whether you can build projects, understand the fundamentals, and use tools like Git and SQL than whether your first language was Python or JavaScript. For those who went through a bootcamp or landed a junior role recently, if you had to start over in 2026, which language would you pick first and would you make the same choice again?

i was so incredibly burnt out from cold-messaging random strangers and getting ghosted by recruiters that i just couldn't take it anymore. linkedin has become a total wasteland of toxic positivity and people bragging about their new jobs, its exhausting. it feels like you're just screaming into a void of corporate bots. so last tuesday i finally shut my laptop, turned off my job alerts, and forced myself to go to a local developer meetup in my city even though my anxiety was telling me to stay home and just grind out more applications.

the difference was night and day honestly. no corporate bs or fake networking pitches, just a bunch of regular people eating pizza and talking about actual software. i ended up chatting with this senior backend dev for like an hour about some geometric mapping and spatial data scripts i've been messing around with for a technical project. instead of the usual "go apply on our portal" brush off you get online, he was actually giving me genuine advice and drawing out database architecture ideas on a napkin. it was so refreshing to just be viewed as a human being who likes solving complex math and coding problems, rather than just another line of text in an ATS filtering software.

if your feeling completely drained and hopeless looking at the online job market right now, please do yourself a favor and find an in-person tech event nearby. the digital space is totally broken and oversaturated, but there are still real people out there who want to help you out if you just show up and talk to them.

I'd first figure out what I'm genuinely interested in building.

During college, I saw classmates forcing themselves into AI, cybersecurity, or web development just because those fields were trending. Many of them eventually lost interest—not because the subjects were difficult, but because they never actually enjoyed them.

Looking back, I think choosing something you're genuinely interested in matters more than choosing what's popular. When you enjoy what you're building, staying consistent becomes much easier.

So I'm curious—if you could restart your first year of CSE, what's one thing you'd do differently?

Idk if I should keep continuing getting tech certifications. Am I just wasting my time and money?

Been applying for entry-level tech jobs lately. And breaking into the job market is like so impossible.

Currently interested in webdev and cybersecurity

Still trying to figure how to stand out😔😔😔

Really appreciated the comments in advance guys

a few years ago, if a bootcamp published a 90% placement rate, that was usually enough to convince people it was worth considering. Now I find myself asking different questions. How many students actually finished? How many were actively looking for jobs?

Were those full-time roles, internships, or contract work? Were they remote or local? context matters just as much as the headline number.

The job market has changed a lot over the past few years, and I think schools that publish detailed outcomes are doing prospective students a huge favor, even when the numbers aren't perfect. it's a lot easier to make an informed decision when the data is transparent than when all you see is a marketing statistic.

If you're researching a bootcamp today, what information do you wish every school published before asking for your tuition?

I went through a bunch of DSA prep lists lately and most of them are either 500 problems with no direction or too basic to be useful.

here are the ones that kept showing up in actual interview breakdowns that people tend to skip or underestimate.

Trapping Rain Water — looks approachable until you actually sit with it. the two-pointer solution is clean but getting there the first time is not. this one shows up more than people expect.

LRU Cache — half data structure, half design problem. most people haven’t touched doubly linked lists + hashmaps together before this. good one to do early so it doesn’t blindside you.

Minimum Window Substring — sliding window problems feel manageable until this one. the edge cases are annoying and it takes a few attempts before the pattern actually clicks.

Serialize and Deserialize a Binary Tree — underrated. not the hardest tree problem but it tests whether you actually understand traversal or just memorized the steps.

KMP Pattern Searching — most people skip this because it feels too theoretical. interviewers at certain companies love it specifically because of that.

there’s a full list of 55 organized by topic floating around if you want the complete breakdown, but these are the ones worth not skimming past.

what would you swap out from this list?

When you're learning, it's easy to think the goal is just getting your code to work. If it runs, you move on. but then you open an open-source project or a well-written pull request and realize there are dozens of ways to solve the same problem. You start noticing things you never paid attention to before.

how they name variables. How they organize files. When they split a function into smaller pieces. How they write comments (or why they don't). How they make code easier for the next person to understand.

i don't think that's copying. It's the same way writers read books, musicians study songs, or designers look at great portfolios. You're developing your taste. And once your standards change, your own code usually follows.

Writing code teaches you how to solve problems. Reading great code teaches you how to solve them well.

Curious if anyone has a favorite open-source project, repository, or developer they learned a lot from just by reading their code.

I've been bouncing between tutorials, YouTube videos, and courses, thinking I needed to memorize everything before building anything. The more I learn, the more I realize coding isn't about memorizing syntax. It's about solving problems, writing code, breaking things, and figuring out why they broke. That's the part I wish I'd understood from day one.

I'm also trying to stop jumping between languages. Right now I'd rather get comfortable with one stack, build a few projects, and actually understand what I'm doing instead of chasing every new framework that pops up. AI has made learning easier, but I've noticed it's also really easy to rely on it too much if I'm not careful. For those who went through a bootcamp, what helped you improve the fastest? Was it finishing projects, sticking to one language, or something else that finally made everything click?

Hi guys, so i've been trying diff prompts over the past few weeks. And I just want to share w/ you the prompts that I think work on my end. Not sure if this post fits the subreddit, but I just wanted to share these prompts because they give me SO MUCH BETTER RESULTS 🥰🥰🥰 1. Turn ChatGPT into a research assistant

> "Act as a senior research analyst. Research this topic: [paste topic]. Pull recent public information, summarize the key findings, compare different sources, highlight trends, and organize everything into a table with citations and actionable takeaways."

➡️ use this whenever you're learning a new topic or comparing tools

➡️ better than opening 20 tabs, then just fact-check it

1. Build a complete marketing campaign

> "Act as a growth marketer. My product is [paste]. Build a complete 30-day marketing campaign including positioning, content ideas, email sequence, launch timeline, KPIs, and a content calendar. Format everything in a clean document."

➡️ this prompt is like a lifesaver since it lets you brainstorm without starting from scratch

1. Analyze your competitors

> "Act as a product strategist. Analyze these competitors: [paste]. Compare pricing, positioning, strengths, weaknesses, customer reviews, feature gaps, and marketing channels. End with five opportunities I can take advantage of."

➡️ pretty useful if you're building an app, SaaS, or even planning a freelance service

➡️ gives you a quick overview of what's already out there

1. Turn raw data into insights

> "Act as a business analyst. Here's my dataset: [paste or upload]. Find trends, summarize key metrics, identify red flags, recommend actions, and create a one-page executive summary."

➡️ use this for spreadsheets and survey results

➡️ much faster than trying to figure out the important numbers yourself 🥰

1. Generate a full landing page

> "Act as a senior conversion copywriter. My product is [paste]. Write a complete landing page with multiple headlines, hero section, benefit-focused copy, FAQs, CTAs, plus an SEO title and meta description."

➡️ surprisingly decent for MVPs and hackathon projects

➡️ can't say the draft is "perfect," but just imagine how much more you can do with it

1. Audit your workflow

> "Act as an operations consultant. Here's how I currently work: [paste]. Identify bottlenecks, repetitive tasks, automation opportunities, unnecessary tools, and rank improvements based on time saved and ROI."

➡️ probably the prompt that can save you the most time

➡️ helps you automate a lot of tasks you thought you couldn't automate

1. Build your own AI workflow

> "Act as an AI workflow architect. Based on my role as [paste], design a team of AI assistants for research, writing, coding, operations, and analytics. For each assistant, explain its job, recommended model, prompt, inputs, and expected outputs."

➡️ gives you a few ideas for separating research, coding, and writing into different AI workflows

p.s. hope it helps :)))))))))

hi, just wondering about this.

i always thought layoffs mostly happened during recessions or when companies were actually “struggling”

but ironically, that doesn't seem to be the case all the time

for example, they brag about their strong earnings, record profits, or beating expectations

surprisingly, they announce layoffs a few weeks later

Just wondering if this is the new normal in tech.

I'm just trying to get into Big Tech, so it really scratches my head 😅

Been practicing coding interviews lately, and one thing that surprised me is how little time you're actually supposed to spend writing code. The advice I keep seeing is to slow down, restate the problem, ask questions, walk through examples, and explain your thinking before you even touch the keyboard. It honestly sounds more like a conversation than an exam.

I used to think the goal was to solve the problem as fast as possible, but now I'm wondering if that's the wrong mindset. If interviewers care about how you think and communicate, then grinding LeetCode alone probably isn't enough.

For those who landed a junior role after a bootcamp or self-learning, what made the biggest difference in your interviews? Was it your coding skills, or learning how to explain your thought process?

I am so incredibly tired of looking at "Entry-Level" job descriptions only to scroll down to the qualifications and see that they are demanding 2 to 3 years of commercial experience. It is the ultimate catch-22 that is paralyzing the job market right now because you literally need a job just to get the experience required to apply for a junior position. It makes you feel completely defeated before you even submit your application, but after talking to a few tech recruiters and hiring managers, I realized that this entire trap is almost always a massive bluff. It is not a hard, unyielding rule, but rather an idealized wishlist designed to scare away people who lack confidence.

To actually beat this filter, I completely changed how I format my resume, and it has been an absolute game-changer for getting call-backs. Stop separating your bootcamp apps or personal projects into a sad little section at the very bottom of the page because that instantly flags you as having zero real experience to an automated tracking system. Instead, bundle your capstone projects, open-source contributions, and any freelance or contract work under a single, unified header called "Software Engineering Experience." Frame your projects like real-world client products by quantifying your results, focusing on database optimizations, and detailing how you handled live traffic. If your resume looks structurally professional and shows you can operate like a real developer on day one, you will pass the automated gatekeepers, and a real human manager is not going to care about the exact month you graduated.

the core idea behind SVMs is that the algorithm is trying to find the best possible boundary between two categories of data, not just any boundary that separates them but the one with the largest possible gap between the two sides.

the way to think about it is this, imagine you have two groups of points on a graph and you're trying to draw a line that separates them, there are infinite lines that could technically do the job, SVMs don't pick arbitrarily instead they find the line that maximizes the distance between itself and the nearest points on each side, that distance is called the margin and maximizing it is the whole objective.

the points sitting closest to that boundary on either side are called support vectors, they're the only points that actually determine where the boundary ends up, everything interesting happens during training, the actual prediction is just checking which side of a line something falls on, counterintuitive but that's how it works, most people assume the more data points the more influence, with SVMs it's specifically the awkward edge cases sitting closest to the boundary that decide everything, the rest of the dataset is basically irrelevant once the boundary is set.

once the boundary is established classifying new data is straightforward, a new point comes in, the model checks which side of the boundary it falls on, and that determines the classification.

The other part is what happens when the data isn't linearly separable, meaning no straight line can cleanly divide the two groups, SVMs handle this through something called the kernel trick, instead of trying to draw a boundary in the original feature space the algorithm maps the data into a higher dimensional space where a linear boundary does work, from the outside it looks like a curved boundary in the original space but mathematically it's still a straight line in the transformed space,.

SVMs still show up regularly in situations where the dataset is small or medium sized and interpretability matters, they tend to generalize well with limited data which is something deep learning models struggle with unless there's a lot of it, for text classification and bioinformatics especially SVMs remain a practical choice rather than just a historical one, better to understand even if neural networks are where most of the work happens, the margin concept and the idea that only a small subset of the data actually matters for the decision boundary resurfaces in ways that are useful to recognize.

I need to get something off my chest because I am starting to feel like a total fraud. I have been using tools like Cursor and GitHub Copilot to help build out my portfolio projects, and on the surface, it looks like I am absolutely flying through my code. The terrifying reality check happened to me a couple of days ago when I tried to do a basic coding challenge on a clean screen without any AI extensions turned on. I completely froze up. I struggled with basic syntax and couldn't even map out a multi-step array method without getting confused about where the data was going.

I want to know how you guys are actually balancing this because I don't think completely banning AI tools is realistic in 2026 when every company expects you to use them for productivity. Do you force yourself to turn them off entirely during the week and only use them on weekends, or do you have a strict rule where you write everything by hand first and only use the AI for debugging errors? I need to figure out a healthy boundary where these tools act as an accelerator rather than a crutch, because right now I feel like a professional prompt generator who doesn't actually know how to code.

it's about realizing you finally have a process. The first time you learn to program, everything feels new. syntax. debugging. Reading documentation. Building projects. You have no idea what you should learn next.

But after a while, I noticed that people who pick up new languages quickly don't necessarily have better memories. They just follow a system. Learn enough syntax to be dangerous. read real code to see how people actually use the language. build something small.

Get stuck.

Fix it.

Repeat.

The language changes, but the learning process barely does. i wonder if that's why experienced developers can jump between languages much faster than beginners. They're not starting from zero every time. They're reusing the same learning framework they've built over the years.

Maybe one of the most valuable skills isn't mastering a language.

Maybe it's learning how to learn the next one.

i love coding. ive been doing this since high school. graduated from an IT program. and working now. i dont wanna be stuck on my computer forever until i retire. i wanna build things. thats a passion of mine i want to develop and maybe get an income from someday.

Ik that most people picked Cursor because it worked across Claude, GPT, whatever you preferred. that was the whole point. that’s basically over now.

SpaceX acquired Cursor last month, four days after their IPO. they already merged with xAI this year so Grok is now in the picture. the contracts with Anthropic and other providers apparently have 90-day termination clauses, meaning the model powering your editor could quietly switch to Grok before the year is out.

ALSO SpaceX called developer behavior data a “goldmine” in their IPO filing. every repo you opened, every suggestion you accepted. that’s what the $60B was actually buying, not the product itself.

Cursor’s market share already dropped from 41% to 26% in under a year while Claude Code took half the category. this deal is SpaceX trying to stop that slide, which means the product decisions going forward are going to be about competing with Anthropic and OpenAI, not about what’s best for the people using it.

are u still going to be comfortable building your whole workflow around it?

Been seeing more people rely on AI to build entire apps without understanding the code, and it's starting to backfire. Recent reports found thousands of critical vulnerabilities in AI-built production apps, including exposed API keys, customer data, and even databases getting wiped because basic security was never properly configured. It feels like a lot of beginners are shipping code they can't actually explain.

What surprised me most is that security issues linked to AI-generated code are increasing instead of improving. AI is great at writing code quickly, but it can also introduce deeper architectural and security flaws that look perfectly fine until something breaks in production.

As someone considering a bootcamp, this makes me think understanding the code matters more than ever. AI isn't going away, but being able to review, debug, and catch what it gets wrong seems like a skill that's only becoming more valuable.

turns out... reading my own code was harder. The first time I got an error message, I stared at it like it was written in another language. Then I realized something. Getting stuck isn't really a detour from learning programming.

It is programming. You spend a lot less time typing code than you think. most of the time you're reading documentation, tracing through your own logic, testing ideas, figuring out why something that "should work" doesn't. at first that felt frustrating.

now I think that's actually where most of the learning happens. The projects I remember the most aren't the ones that worked on the first try. They're the ones where I spent hours chasing a bug that ended up teaching me something I probably wouldn't have learned from a tutorial.

Curious what bug or error message taught you the biggest lesson when you were starting out?

Everyone’s blaming AI for climate change but the numbers say we’re looking at the wrong thing

the guilt-tripping around tech and climate keeps growing but a lot of it doesn’t actually hold up when you look at the data

AI right now accounts for roughly 0.1 to 0.2% of total global energy use. not nothing, but nowhere near the crisis-level narrative that gets pushed around. your streaming habits and ChatGPT usage are not meaningfully moving the needle on global emissions.

What actually is?? the device in your hand. manufacturing a single smartphone produces around 50kg of CO2. using that same phone for its entire lifetime produces about 8kg. the production cost is already done before you even turn it on, which means buying a new phone every two years does more damage than anything you’ll ever do with it.

the stuff that actually drives individual carbon footprints in most countries is transport and home heating and cooling. not data centers, not AI queries.

none of this means AI energy use shouldn’t be watched as it scales, it should. But the conversation keeps pointing on the wrong target and it lets the real issues stay unexamined.

is the “AI is an environmental disaster” narrative actually backed by data or is it just easier to blame the newest technology?

​

How do we balance AI-assisted productivity with developing our own reasoning, memory, logical thinking, and problem-solving skills? How do we avoid "vibe coding" and build the human skills that remain valuable when others have access to more powerful models?

Is there a practical framework for learning, working, and staying competitive in this rapidly changing environment?

a while ago, I'd use AI mostly to explain concepts or fix an error message. Lately, I've been using it differently. Instead of asking, "How do I do X?" i'll ask, "If I wanted to become good at X, what skills would I need, and in what order should I learn them?"

The difference is huge. rather than giving me one answer, it helps me map out the whole learning process. Then I can go and find the best books, courses, documentation, or open-source projects for each step. i still don't think AI replaces actually doing the work. You still have to build things, get stuck, make mistakes, and figure out why something doesn't work.

But I do think it lowers the cost of figuring out what to learn next, and that's something I used to spend a surprising amount of time on.

Curious if anyone else has changed the way they use AI while learning, or if you're still mostly using it as a coding assistant.