3 ms·
I disagree. There are things that should be required for a software engineer to know. Queueing theory comes to mind
by HidyBush 4y ago
I disagree. There are things that should be required for a software engineer to know. Queueing theory comes to mind
- cr3ative 4y agoI'd wager any problem involving queuing theory could be googled/researched in under a day. Hard to call it a requirement when you can just.. look it up when you need it.
- soco 4y agoIs there any topic which cannot be googled in one day, civil engineering included? I certainly hope nobody employs "googling engineers" in anything requiring, ahem, "engineering".
- IshKebab 4y agoQueueing theory is a weirdly niche thing to require. I guess almost nobody is a software engineer according to you!
- deleted 4y ago[deleted]
- HidyBush 4y agoQueueing is niche? If you have to program ANYTHING that serves requests and has a limited buffer you enter the domain of queueing theory. Processing internet packets? Queueing theory. Developing a distributed system? Queueing theory. Designing software to manage a call center? Queueing theory. Shipments? Ticketing? Payments? A myriad of other things? Queueing theory. Fun fact, while posting this reply HN redirected my to a page "Sorry we're not able to serve your request this quickly". Guess what would have helped? Queueing theory.
- IshKebab 4y agoSure you could analyse all of those things using queuing theory but with the exception of distributed systems, TCP etc. and maybe super large scale distribution (e.g. Amazon warehouses), you 100% do not need to. What exactly is queuing theory going to tell you about managing a call centre? Why would I need to know some deep theory to be able to stick calls in a FIFO and deal them out to agents? Are you just proud of having studied queueing theory?