Live data from Hacker News

Viewing profile — mak4athp

mak4athp

HN member
Joined
Wed, Apr 15, 2015, 10:38 PM UTC
HN karma
51
Public activity
36 items

About mak4athp

No profile information was provided.

Recent public activity

  1. comment
    Comment #9490506

    As you may have puzzled out from other responses here, that's a very personal question. You need to figure out the cultural details that mean something to you, then ask the questio…

  2. comment
    Comment #9490493

    If you carry this attitude through a series of future jobs, you're going to demonstrate that you're a pretty awful employee. Not all work is exciting, and new hires are often going…

  3. comment
    Comment #9490471

    It's extremely hard to sell a novel "job title" as a consultant. Most clients will want to see examples or case studies of your success in the role -- so that they can understand w…

  4. comment
    Comment #9490459

    You don't realize it yet, but you're expressing a ton of anti-patterns here. Not the least of which is an urge to prematurely optimize your project, and desire to invent your own n…

  5. comment
    Comment #9490435

    As a full-time employee in the purely technical track, greater responsibility and pay would come through architectural and design roles. If he really just wants to code, the best w…

  6. comment
    Comment #9489549

    Which of the above suggestions wouldn't apply to both? I understand what you're saying in general, but there are a lot of universals that would apply across all kinds of jurisdicti…

  7. comment
    Comment #9488350

    You recognize the irony here, right? You won't give everyone the benefit of the doubt, but only take seriously the people who offer it to you. That strategy doesn't seem like it wo…

  8. comment
    Comment #9478042

    There's a real difference between a Customer and a QA member, though. You can't demand leave the responsibility to make a good report on a customer because they're external to your…

  9. comment
    Comment #9476044

    Everybody has different needs and expectations. Some of those even evolve or 180 over the course of a single career. Speaking to your own concern, the tradeoff is that many technic…

  10. comment
    Comment #9475954

    I think your intuition is correct when you suggest that this approach isn't scalable. It runs counter to the concept of "flow", articulated in Peopleware[1] 30 years ago and confir…

  11. comment
    Comment #9475785

    I personally agree with you, I just find that you/we are in the minority as hiring managers. When you hire a PHP person to join your Ruby team, you're making a bet that they're abl…

  12. comment
    Comment #9475584

    If you pursue a specialization and get bored, you move on from it. There's not a lot of drama to it and a lot of your skills will be transferable. On top of that, it sounds like yo…

  13. comment
    Comment #9475463

    > otherwise merit-based processes What a delightful thought experiment! In the meantime...

  14. comment
    Comment #9475340

    Not really. For internal use as algorithm fodder, they've got millions of photos to harvest from Bing. And for external use, they can't confirm that the submitter actually had the …

  15. comment
    Comment #9475328

    Do you think there's really an answer to your question that would make you reflect on the issue? If so, what might the answer look like? If not, why did you ask the question?

  16. comment
    Comment #9475285

    You generally need to bring an applicable skill to the table immediately on hire. With the exception of a few stable mid-sized companies that really love generalists and cultivatin…

  17. comment
    Comment #9474982

    Deciphering bad bug reports is absolutely a waste of your time as a developer, but that doesn't imply that the user is mistaken. In nearly all cases, the user is correct in sensing…

  18. comment
    Comment #9474964

    If an organization is having developers triage vague bug reports directly from end users, they're already in trouble. Not only are developers a very expensive resource, they're gen…

  19. comment
    Comment #9467300

    1. Figure out what sector/industry you'd like to work in. 2. Figure out what's popular in that sector 3. Focus your skill development on that. With some exceptions, but there's a h…

  20. comment
    Comment #9467079

    Whatever strikes your fancy. If you're pursuing startup culture at your age, and you aren't trying to become a developer/engineer yourself -- you have all the freedom in the world.…

  21. comment
    Comment #9467040

    Given where you are in your career, you're inevitably a high-risk person to hire for contract work. That means that at least one of the following will be true: * you'll be ignored …

  22. comment
    Comment #9463432

    > Then again, if I'm hiring a rockstar engineer ... If all they want to do is come in for 6 months and crank out some projects and leave, I'll probably still be grateful to have th…

  23. comment
    Comment #9463420

    > Tenures too short? Maybe they delivered a lot of value in 6 months and were ready for a new challenge. Would you not hire a builder to build your house because they did the last …

  24. comment
    Comment #9456121

    While you may not feel privileged because you had to make hard sacrifices, not everyone is in a position to make the sacrifices you made. But even then, your anecdote only speaks f…

  25. comment
    Comment #9455726

    1. Don't use the same password everywhere. 2. Use a password manager like LastPass or 1Password. Regardless of the incidental security risk of showing those rules, the site shouldn…