My company completely mismanaged a project, meaning it had no chance of launching succesfully, then decided to move the project launch date forward 2 weeks before launch because they had scheduled a trip and wanted a 'a better atmosphere at the party'...
I think if they are a dev they wanna see you problem solve and if it's just hr they wanna hear techno mumbo jumbo for a couple of minutes spoken confidently
Every year, the company I work for fires 50-100 ppl. They don't really fire anyone from the management team. Right after that, they start hiring again, so next year same time the company has the same amount of employees. This happened in the last 3 years every year. The funny thing is, no one in the management knows what the fuck to do, because they are not qualified for anything, and were pulled in by a friend. It's a company that runs 100% on technology and web services the developers built. And in the same time they fire the devs who actually built all the stuff. Now there are barely anyone who knows how anything works. Everything is full of bugs, the whole development workflow is a joke - for example; no local development, the code is tested first on the staging server, and this is a big company
"Well then, i correct my previous estimate to a XL Tshirt-Size or 10 Story Points and lets meet in the middle at a solid 7 Story-Points this week and a solid 2 Story Points next week for any incoming disturbances like unneccessary PM Meetings"
Personally not a fan of stand ups. 😅 Sit-downs are perfectly fine. Maybe once or twice a week depending on the complexity, how many people are involdved and the overall timeframe.
to be honest profesional knowledge is based on working with something for 8 hours a day. If you spend 16 hours coding per day, it makes it a two day experience. Or at least thats how Imagine it works and thats why i put more time than normal on coding knowledge.
A lot of my batch mates who are web devs got lay off just a year into their job. I worked in hardware and we rarely have layoffs because it's harder to train us but I can't be complacent
I am a fullstack programmer, and I sitting here and thinking, sure no problem. I have made databases from nothing, as well as the entire front-end. So yeah. It is just like switching from anthropology to psychology, while switching from Korean to Chinese. And that was actually exactly how I wrote my master's thesis. 😅 It was about my brand new theory within Sociology. 😊
An interview I had back in February had me do a bunch of java programming exercises, some of which were pretty complex, without any access to documentation or help of any kind. I was told the interview would be in C++.
A problem as old as time, back in 99 it was common to need 5 years of java experience. I've decided these sort of requirements are a test to weed out developers who are too autistic to lie, and so it is ok to just tell them whatever they want to hear because they definitely wont hire you if you hurt their feelings by correcting them.
No sure what a dynamically nested linked list is, but if it's a tree, then sure, I actually had to write a function to flatten ( or normalize ) a tree structure into an array of nodes with each each node contain a parent node pointer. It's rare that you need to actually do this, but it still happens time to time.
Designer here and i have a couple of points 1. We try to maintain consistency across all net new components so that this kind of thing can get fixed once and not come up again. It becomes an issue when there are a lot of small things wrong in a lot of places. Fix it once and reuse the component so this kind of (admittedly) stupid issue isnt discussed again. Secondly, YES! This is my exact issue with designers - small shit like this does not matter. My job would be to understand what to show on the dashboard and make sure users are able to use it to get the value they need. I would need to find the right things to show users, give them the customizability needed and visualize the data in a helpful way, all while working with dev to make sure it doesnt take 5 years to build and we can output the smallest package of work to get the most benefit. Designers who prioritize pixels over functionality give us all a bad name
I had a similar experience. I have 10 years of experience in various backend languages. I applied for a Golang position, a language rarely used in our country. I got an interview, but for a Java position. They denied me the Golang position because I hadn't worked on a professional project with it in the last 5 years. My private project didn't matter. HR didn't want to burden the project manager with hiring an inexperienced Golang developer. The fun fact is, I hadn't used Java in the last 5 years either.
