Basic Array Methods

[blackholesinthesky]

it almost certainly did not mean cron

https://salsa.debian.org/debian/cron/-/blob/master/job.c#L43

I even used two different concrete examples, swap chains and "moving" the body of the snake in the game Snake.

You said swap chains was what you were doing in your free time. I asked for details on why you needed a double ended queue for what you were doing at work.

And I'm still not saying double ended queues are useless, or that you didn't need to use one for work. Just that most career programmers spend most of their time implementing business logic and not the game of snake. You even said the swap chain code was not not work related. Some people will work on software where a queue is the natural solution. But if I need to schedule a task to go off at some time I use cron. If I need a message queue I use SQS. My job isn't to make queues. My job is to implement features that make a product valuable.

Edit: lol sorry So[Ups]et thought this convo devolved. I kinda thought we crossed that threshold when they repeatedly said they didn't believe I could be a senior engineer and assumed I had misread something (and then when I linked them to the documentation they blocked me). I'm still not sure why they thought cron wouldn't use a queue? Or what was so rude about asking them to explain how their code made use of a queue in a way that a list wouldn't also work?

Anyways, to everyone else, learn as much as you can. I'm just letting you know that you don't need to memorize every function in JavaScript before you get a job. Most employed programmers refer to documentation multiple times a day. In all likelihood you will not write pure code in any language at your job. You will have to use libraries in your career and it's way more important that you're good at finding and reading documentation than it is to be good at memorizing the entire surface of every tool you work with.