If you can read this you are too close

  • 0 Posts
  • 27 Comments
Joined 5 months ago
cake
Cake day: December 7th, 2024

help-circle
  • I think nobody understands exactly how anything works, but enough of us understand our own little corner of tech to make new things and keep the older things going. I’ve been coding for decades, and proudly state I understand about 1% of what I do. This is higher than most

    AI will make these little gardens of knowledge smaller for most, and yet again we, as the human species, will forever rely on another layer of tech.






  • In some situations with some people yes. It’s really hard to separate the project and team.

    Usually, projects I have seen start with the best plans and methods, or at least vague good intentions, but later pretend they never met them. Like a cheap date.

    There are some projects that naturally lend themselves to one approach or other, and they last longer following the original guidelines ; but if a project lives long enough these guidelines become the enemy.

    I think the only projects that follow any set of guidelines for longer than a few years; they have a narrow purpose for being. Straightforward evolution or needs






  • This, what you said, is so important. In my years doing my own business, I have had literally hundreds of scammers, some smarter than me. Its best to just not even try to talk to people trying to contact you first in these platforms.

    And many many scammers will post jobs, and one cannot tell by seeing if this is a new account. Some of my multi year assignments have been initiated by sketchy new accounts. At the same time existing accounts of clients usually have their own preferred coders. If you get to talk to an existing account with a history, check out the reviews and be wary. There may be a reason they are seeking out new blood.

    I think its ok to go off site to talk to the new job candidates. Often, cannot have decent conversations in platform. And an in depth talk is free for all, and will often give clues in the first few minutes of talk.


  • (edit formatted)

    Things I learned the hard way:

    • Never agree on anything until can see the existing code and talk about everything.
    • Milestone payments only. Stay away from any lump sum payments or percentage cuts.
    • Full payments in escrow first.
    • Never reply to people you don’t know who seek you out, only seek out jobs.
    • In first contacts ask questions first, don’t talk about qualifications. If questions good then customer knows you know the tech well.
    • Learn to walk away if instincts kick in

  • Freelancer platforms that have paying stuff do exist, but it requires effort to learn how to use them; and during the long learning curve, one is usually grossly underpaid and sometimes scammed and or cheated.

    If in financial emergency it’s often better to not try this and try menial work outside industry. But one can find it as a decent resource stream after some trial and error which can take a year or more to learn


  • Back in my day, there were no guides; except for books that had to be bought or borrowed, one learned by hacking code until it worked or, better yet, had a helpful person in the same room give tips.

    After the internet came into being, there started to be guides, at first many were ok. Then people realized they could write slop and make money or get internet points or credit. So now here we are, today, with many horrible tutorials, some middling, some good ones, about to be buried by AI