| General > General Technical Chat |
| Giving interviews, disappointing, am I getting old? |
| << < (5/7) > >> |
| paulca:
--- Quote from: Brumby on October 21, 2021, 11:31:33 pm --- --- Quote from: Fgrir on October 21, 2021, 09:40:00 pm ---There is only one combination of a shuffled deck of cards and writing a program to generate it should be trivial. Now permutations is another story, or combinations of a 5-card hand dealt from the deck... --- End quote --- I would't respond like that. You would risk being labelled a smart-arse. --- End quote --- This is the point. It forces a decision, a choice, a thought process, even an opinion. I find those qualities more lacking than the technical 'does this do that'. Too often I find people almost brain washed into their silo of one framework, one mindset. As one specific; when you ask Java developers about any negatives with "their" frameworks on performance including memory load or any kind of efficiency they go blank. The same candidates when then tell their stories of high performance networking talk of 100s or 1000s of message or responses per second and latencies of milliseconds. When you point out, your domain is deal with microseconds. Their multi-threading/performance understanding pales. I interview from junior to 5+ years specific roles. However I would expect a 2-3 year Software enginerr to have some understanding of the costs of such "frameworks". And all I see is they simply don't understand at all. They don't understand the maintenance overheads, the debugging overheads... yada, yada. It just makes me worry I'll end up cleaning up after them. |
| paulca:
At the same time, customers love them. Throw a PoC together in 2 weeks, consider it production ready.... why can't we have MORE younger inexperienced people in our team, they get stuff done. |
| nigelwright7557:
Sometimes people are looking for someone who knows it all when a lot of the time you dont need to know it all. I have been writing software for 40 years, the first 20 without any training and all my systems worked. Been in electronics 40 years too. Only got City and Guilds in industrial electronics yet designed many computer systems. In 1983 I was given the task of writing some Teletext software yet had very little experience of Z80. When your given a serious task you learn very quickly or give up. The reason I got the job then was because programmers were then thin on the ground or what there were, were expensive. These days its harder to get away with knowing little. To even get a web programming job you have to meet a long list of prerequisites. HTML, ASP, CSS, bootstrap, java script, entity framework, SQL server, mysql etc etc |
| Kjelt:
My biggest concern with the young generation is to keep them interested to stay. We have only huge piles of spaghetti C code to maintain that has been developed over decades and most of them are not interested in C programming. They want "cloud dev", "big data", C#, they walk out after a few months. We can't get the message through to HR to tell them at the interview what to expect, prepare them for our department. We get a new colleague each quarter and we keep loosing them worst case a quarter later, best case a year later. The funny part is that the managers also leave every 14 months, the last one had a record at 5 months before jobhopping to the next step on the careerladder. Time to ask for a big salary raise to my current manager, if I and my two colleagues who have been there for the last ten years walk, the product is dead :o |
| Nominal Animal:
--- Quote from: paulca on October 20, 2021, 06:58:16 pm ---It's why I am creating a set of code tests, one of which includes this: Write a program to generate all combinations of a shuffled deck of cards. The right answer IS "No". The "better" answer is realising its impossible and explaining why. --- End quote --- I'd fail, then, because I'd give you a function that takes a 226-bit unsigned integer (0 to 52!-1, inclusive), and returns a deck with that particular order. The reason is that generating all combinations in a sequence is rarely useful, but being able to generate any specific combination (here, any specific configuration in the 52! -point configuration space), i.e. any one of all the combinations, can be useful. In particular, when examining how some specific patterns of shuffling affect the deck order, how long loops they generate, and how large a fraction of the available deck configuration space the shuffling can cover. Even after decades of experience, I still fare so much better when I'm presented with an actual, real world problem, and can solve that one instead. |
| Navigation |
| Message Index |
| Next page |
| Previous page |