4 ms·
Well if your targeting small companies I would order them JS, Java, C#, in terms of languages. If you would like to be working for an enterprise company probabl
by ChuckMcM 13y ago
Well if your targeting small companies I would order them JS, Java, C#, in terms of languages. If you would like to be working for an enterprise company probably Java, C#, JS. Of course given adaptabiilty it doesn't really matter, you can learn what you need.
This is more worrisome though : Presume that I'm both willing to telecommute or relocate, and up for anything from founding a company to working as a faceless code-slinger.
When folks tell me "I'll do anything" I'm left wondering
If they are a contractor, its all up front, they are a money to code engine, pour in money on one side, get out code on the other. As the going in position for a full time employee I wonder, "Is this just a paycheck? Or do they have any goals they are trying to achieve?" I've known folks who just wanted a paycheck because their passion was something they were doing outside of work, and that works well on a contractor basis, but less well on a FTE basis.
I may be unusual but if someone is working for me I want them to be getting something more durable out of their efforts than just a paycheck. New skills, new experiences, moving some personal goals closer to reality as they relate to their career. (that last bit is important because clearly moving closer to a goal of "home ownership" is a solid goal, but as a manager my tools there are limited :-)
So being flexible is a plus, but not knowing where you are going is a minus. An example of "going" is this, let's say you wanted to learn how anyone could build a web service that serviced a billion users, and Facebook was the only place where that happened. You could learn the language and frameworks that Facebook used, and the stack, and the systems management, and all the places where scale negatively impacted the user experience and how they fixed that. (unlike Google they are very open with this stuff so its easier to do from the outside). That is a goal and then the languages and frameworks fall out of the goal. Or a goal of "making the connection between writing and publishing more seamless" which will have you looking at Wordpress and Ghost and Tumblr Etc as frameworks and languages where people were trying to achieve that goal, did it work? Did it miss? Where could it be better?
Hard to describe, but it is not unlike someone coming up to you on the street and saying, "Excuse me, should I drive down that street, that one, or take the freeway?" The answer is meaningless unless you know the destination.
- derefr 13y ago> Hard to describe, but it is not unlike someone coming up to you on the street and saying, "Excuse me, should I drive down that street, that one, or take the freeway?" The answer is meaningless unless you know the destination. Actually, that is exactly what I was asking, and it seems like a perfectly sensible question to me. (Though it's not a question you'll encounter every day.[1]) I think you're ignoring what, exactly, a minimax algorithm entails: it's not a goal-directed least-cost search, like, say, A⁎. Instead, it's more about picking and weighting a set of potential goals, given the costs involved with pursuing them. So the question becomes, in effect, not "what road should I take to get to X," but rather, "which road should I start heading down, assuming I'll narrow down the set of possible Xes I might want to pick later, that will cause me the least problem for any given X I might have chosen?" Oddly enough, this is a question driving-directions programs have a heuristic for. If you chart a course, on e.g. Google Maps, between suburban addresses in two different cities, the directions will almost always start with what amounts to "first, get out of the suburbs, so you can reach the highway." Given this, without knowing where you're going, "get out of the suburbs and onto the highway" is a high-value guess in how to get there.[2] You might be wrong, of course: the place you might like to go might end up being in the same neighborhood you were already in. But, across the set of all possible destinations, you'll regret the strategy of heading to the highway less often than you will the strategy of "sit in your driveway waiting to see where you're supposed to be going." --- [1] It's kind of an inhuman way of thinking, really. Humans tend to come with both "axiomatic" terminal goals, and deontological notions of how they have to get where they're going. Minimax solutions only become relevant when, for example, you've decided that what you'd like to do with your life is "to pursue, in a consequentialist manner, the maximum amount of money-earned-per-unit-time, so I can then engage in effective altruism." ;) (More generally, though, every real-world question people deal with where they want a "good answer that leaves my options open" is actually a bit of goal-directed search, and a bit of minimax. You do want to invest effort getting to X; but you don't want to have invested too much, if it turns out X is closed, or your friend wants to meet at Y instead.) [2] Actually, I just thought of a real-world scenario for this. A lot of jobs (e.g. truckers, ambulance drivers, taxis) involve a combination of a driver and a dispatcher, where the driver has to be ready to get "anywhere" the dispatcher might tell them to go. If dispatches come in steadily, then the driver must simply travel directly from the end of whatever route the last dispatch took them on to the beginning of the next. But if the driver has enough time between the end of the previous dispatch, and the start of the next, then where should they drive toward, optimally, to wait?
- ChuckMcM 13y agoNice! You are correct of course, I did mis-understand your question. I suspect the minimax answer is Java. My reasoning for that is that enterprise shops both consume and turn over a lot of Java programmers, this is in part to consulting gigs with Salesforce, SAP, Oracle, or IBM. Thanks for the clear response and your excellent example. It is interesting to see what it optimizes for. I don't doubt you could stay employed "forever" at $45,000/year Java shop code monkey jobs for example. My personal conjecture is that Tech is not a 'connected graph' in the sense that not all nodes are reachable from any node, and not all paths can be traveled in both directions. The example I am most familiar with is 'CEO taint' which is folks who get to a certain level, and then become CEOs of their own startup, where they reach a certain level of qualified success. Then, in a quest for finding their next engagement they are un-hirable because 'former CEO' isn't something you higher in to be a coder, and maybe not manager. Their only accessible nodes are 'new startup' or 'appointment as CEO to startup' or 'consultant'. If you can't get funding for a startup, and you don't have enough street cred as a 'consultant', its a really sticky place to be. The other common one I've seen is people who 'grew up' in a company, started right out of college and put in 10, 15, or 20 years, and then left as UberDistinguishedPrinciple Engineer/Scientist but were unable to find anyone who would hire them at a level and salary they could easily accept. But I'm wondering how much of that transition resistance is simply pride/wages related.
- phaus 13y ago>When folks tell me "I'll do anything" I'm left wondering. Not everyone is a delicate little flower that requires every aspect of his environment to be perfect in order to come to work, bust his ass, and keep a smile on his face. Some people love to program and don't really care where they do it or in what language. Sure, there are languages that hn loves to hate, but in every such case, I'd bet that there's someone out there that's a better programmer than you that fucking loves it. To be clear, that's a statement about diversity in opinion, not an attack on your skills. Other perfectly talented people have a hard time finding a job and just want a chance to show someone what they can do. This is the situation that a lot of people just starting out are in, but there are also experienced people who for whatever reason, struggle to find employment. Not sure if you have experienced unemployment, but its terrifying. It shouldn't come as a surprise that people put survival above finding a perfect job. People shouldn't default to the assumption that people who have a hard time finding work must somehow be defective.