Make the company seem like their vetting process was "Google like" and "trendy" Various interviews had me solving what I consider not only impractical, but almost silly puzzles / math problems that not only didn't apply to the company I was interviewing with, but didn't apply to anything real-world - it felt like it was a way to: Guess what, not only did my age hinder me (I'm 53), but my lack of CS math background seemed too in an interview process. I had a three year earn out, finished that and decided to get back into the workforce and get a job at a senior or above level (thinking Director, Manager, etc). All the while, still writing code, building product, etc. The last one, I ran engineering which had 25 developers and we shipped a brand new product to market and I helped sell that company (the company that bought me out) to a larger company. I've had two successful exits since the early 2000's, most recently one that of a company that I built, wrote the product for and sold to a company in 2014 (all modern web based stacks, technologies etc). I sometimes get a bit depressed that others don't consider it a "hard" (and therefore interesting) problem. It dwarfs any of the other problems I've tried to solve. This is the hardest problem I've ever worked on by far. Hanoi towers codewars code#You sometimes dip your toes into solving problems in other domains, but the biggest value you can give as a programmer is in creating a code base that is both simple and sustainable (and keeping it that way). I feel that programming is more about handling complexity than it is about solving other problems. Their work was highly theoretical, but they had electrical engineers doing the research (and were actively collaborating with a university). My brother worked in a company that was doing circuit board design (simulating crosstalk, etc). I've occasionally been asked to solve some hairy caching/concurrency problems, but again I've gone straight to the literature. The best example might be when the team I was on did shape recognition from hand drawn shapes to shape objects in a drawing application. In my career, we've done a couple of things that would be considered "hard", but in each case we've leaned heavily on papers published in academia. "Hard problems" are risky business ventures. and is one of the best architects I know. One of my best friends who I worked with across three jobs graduated from one of those infamous for profit schools, for years wouldn’t know an algorithm if it hit him in the face, but spent a lot of time on side projects, reading best practices from books, etc. Hanoi towers codewars how to#I came up as a traditional computer geek - learned how to program in Basic and assembly on an Apple //e in middle school, fell in love with C, spent way too much time on comp.lang.* groups etc. I’ve gone on lots of interviews with only two rejections - the rest I took my name out of the running once I got the job. That was actually important since we were writing cross platform, C that had to be highly optimized. The closest I came to a CS style interview was my second job out of college when I had to explain high level different data structures. Hanoi towers codewars software#My last three jobs I had to whiteboard an architectural diagram of a system, come up with a 90 day plan to create a software development team (I didn’t know I was applying for a lead position), and describe how I would introduce Devops, redundancy, traceability, etc into a system Hanoi towers codewars professional#I’ve been a professional developer for 20 years and have never had to recite CS algorithms or solve obtuse problems. Forget any of the rest of your skills, because we all know the only thing that matters when interviewing is an ability to recite CS algorithms out of memory and solve obtuse puzzles while pretending you've never seen them. You just use sort().Īnd that's okay! Inventing new algorithms with theoretical significance is not your job! You have other skills and they're of much more immediate value!Įxcept when it comes to getting a job. You don't know how to compose and compare sort functions for abstract sets of N elements because you never needed to. You learned to develop applications, research API's, study trends, and participate as a team member in development workflows under commercial pressure. Importantly, it was less grooming than someone who studied something like English or Sociology or History, but it was still a different discipline than what the job market demanded. Universities traditionally focused on Computer Science and their graduates would often need a lot of grooming before they could really be independently and reliably productive in the commercial words of application development or software engineering. etc) sometimes use the same tools but are all different disciplines. Think of it this way: application development, software engineering, and computer science (and data science and.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |