In uni, we get taught tech stacks, algorithms, and writing code, but profs doesnt really talk about the actual corporate machinery that goes along with it.

I keep hearing jargony terms like Scrum Master, Sprints, Standups, Syncs, and builds, stuff you only really get exposed to once you're actually in the industry.

For those already working in tech: what are the real-world corporate processes, workflows, or unwritten rules you wish someone had explained to you while you were still in school? like the stuff that actually caught you off guard when you were first starting out?

So I have been working as a PHP developer for around 4 years now, mostly laravel and some wordpress stuff. Honestly I like the work but the pay just isn't growing. Every time I look for a new job PHP riles pay almost the same as what I am getting now and the better paying ones are all asking for node, python, java or Go.

I am in INDIA if that changes something.

Now i am confused whether I should switch to another language or just stay in PHP and try to get into a better company. I dont want to spend months learning something new and then end up starting from zero again.

Anyone here who switched from PHP after a few years? how did it go for you? did companies count your old experience or did you have to take the junior role?

Would really appreciate some honest advice.

I’m trying to understand how teams deal with N+1 queries in practice.

The pattern I mean: a page loads 20 orders and, for each one, fetches the customer on its own.

SELECT * FROM orders ORDER BY created_at DESC LIMIT 20      -- 1 query
SELECT * FROM customers WHERE id = ?                        -- x 20

That’s 21 queries instead of 1 or 2. If each round trip is around 2 ms (an assumption), it’s about 42 ms against 2 to 4 ms with a join or a batched IN query. With 200 rows it’s 201 queries, so the cost grows with page size.

What I know so far: a join or a batched query fixes it, but a join that loads a collection multiplies rows, and combining it with pagination can force some ORMs to paginate in memory. Eager loading everywhere can also load data you don’t use.

My questions:

1. Do you assert query counts in tests, and if so with what tooling?
2. Do you rely on ORM statistics or debug logging, or on production monitoring?
3. At what point do you consider it worth fixing: any time you see it, or only after measuring?
4. Have you found cases where the “fix” made things worse?

If I’ve got something wrong here, please correct me.

I don't use reddit so new account new everything but I know that this has to be the place for help.

I'm taking an intro to programming course but I need a windows computer for VS Code and .NET framework (whatever that means I really have no idea). I have a Mac. I did some googling and saw that I could use Windows with UTM. Tried it. Got confused. Made this account.


I have no idea what I'm doing and could really use some help.

I want to become a developer and Im just unsure about university. One school may be "lower tier" and has a lower math barrier, while the other is "higher tier" but has a weird amount of math for software development (same load for a CS degree)!

I’m just curious as to if any of your employees have cared. Thanks!

This isn't strictly a programming question, but I think programmers are well suited to ask.

I basically want to get better at using computers. As a background: I know some basic programming (C++, python) but nothing fancy.

I specifically want to learn how to use the command line effectively. I am currently using Windows, but I am planning on moving to Linux (and it's my understanding that you use it a lot with Linux?) but even in Windows it seems very powerful. Any good resources for getting started?

I would also like to understand how GitHub works. While I am not very good with computers, I use mine a lot for various things and I often find myself searching for very niche programs.

This usually leads to a GitHub page, and often there's not like an executable to download and run, and I never really understood what you are supposed to do (maybe it depends heavily on the application?). Here I don't even know what it is I don't know, so it is a bit difficult to ask for specific help, but I guess if anyone has tips for basic (or advanced for that matter) computer skills that will help me here, that would be much appreciated.

I do not get Minesweeper. I have tried coding it in Javascript and do not get the functionality. It seems like an interesting concept, but seems to not have good logic seems very random.

I've got a small public site where people can write into a shared page without signing up. No accounts on purpose. That also means I can't ban "a user," only a browser session or an IP range, and both of those are cheap to burn.

Right now I do the usual anonymous stuff: Cloudflare Turnstile on session mint, a short proof-of-work, a non-exportable device key in IndexedDB, rate limits, and a rotating refresh cookie. It slows down dumb scrapers. It does almost nothing against someone with residential proxies and a Turnstile solver farm.

Is there a durable approach here that isn't "add login"? Things I've seen tossed around:

- tighter per-/24 and IPv6 /64 device budgets

- behavioral signals (pointer rate, paste vs type) with a step-up challenge

- voiding votes from revoked devices at tally time

- Web Bot Auth for known agents (read-only)

What have you actually shipped on a no-account product that survived real abuse, not just load tests?

Site if it helps to see the shape of the problem: https://sharedpage.app

So we use a browser based design software at work. It generates an install report of parts required for a job. We have approximately 300 jobs during the calendar year. I was hoping someone would be able to direct me to a software that would allow me to take the install report (PDF) of multiple jobs and tally standard parts. The current way of doing it is tedious. Pointing me in the right direction or suggestions for a different sub would be helpful. Thanks for your time.

I've been learning programming for about a year and eight months now. So far, I've learned HTML, CSS, JavaScript fundamentals, and Python. I've also built a few projects, including some games, so I have practical coding experience. Currently, I'm learning React, and I'd consider myself somewhere around the intermediate level.

However, there's one problem that's been frustrating me lately...... I feel like I spend far too much time solving problems and debugging code.

Sometimes, I get stuck on a particular piece of logic or a bug and end up spending two or three hours trying to figure it out. Meanwhile, I could probably write hundreds of lines of code in that same amount of time if I already knew what to do.

I understand that debugging and problem-solving are essential parts of programming, and I'm not expecting everything to come easily. But I want to become more efficient at breaking down problems, understanding errors, and finding solutions without getting stuck for hours on a single issue.

For those of you who have been programming for a while, how did you learn to code faster? Are there specific habits, problem-solving techniques, or practice methods that helped you improve your speed and efficiency?