• 1 Post
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • Remember that you are also interviewing them. They won’t expect you to know all the answers, but will want someone that they can work with. If you can, answer questions with the STAR method (situation, task, approach, result), but don’t waffle. You can use one piece of experience in a variety of ways: teamwork, research, urgent deadline etc.

    It’s ok to say that you are nervous, they should try to put you at ease.

    You may be asked ‘trick questions’, these are not usually to to you up but to see how you work an unknown problem. There is no right answer. Not knowing stuff is ok. Not being able to think up a plan is less so.

    Remember whatever the outcome, this is really useful experience. See if you can get a site tour, ask about the tech used… You can then add this to your knowledge for later. In my experience, industry is frequently several years ahead of academia so you get a good chance to understand the real world.


  • I’d go with a good quality traditional key lock fitted properly in a good door and frame. Security isn’t a single point task, it depends on many things so think like a bad person and do what you can to make your property a harder target than your neighbours.

    A good lock on a bad door doesn’t work, neither does a bad lock on a good door. Everything needs to work together. If you’re likely to lose your keys or many people need access a smart lock may be an idea, but good probably isn’t cheap. If it’s just you and you can keep your keys safe, then I think tried, tested and simple kit is good.

    Ultimately though, as ever, it’s your risk assessment based on your needs.













  • All the other comments are great advice. As an ex chemist who does quite a bit of code I’ll add:

    Do you want code that works, or code that works?! It’s reasonably easy to knock out ugly code that only works once, and that can be just what you need. It takes a little more effort however to make it robust. Think about how it can fail and trap the failures. If you’re sharing code with others, this is even more important a people do ‘interesting’ things.

    There’s a lot of temporary code that’s had a very long life in production, this has technical debt… Is it documented? Is it stable? Is it secure? Ideally it should be

    Code examples on the first page of Google tend to work ok, but are not generally secure, e.g doing SQL queries instead of using prepared statements. Doesn’t take much extra effort to do it properly and gives you peace of mind. We create sboms for our code now so we can easily check if a component has gained a vulnerability. Doesn’t mean our code is good, but it helps. You don’t really want to be the person who’s code helped let an attacker in.

    Any code you write, especially stuff you share will give you a support and maintenance task long term. Pirate for it!

    Code sometimes just stops working. - at least I’m my experience. Sacrifice something to the gods and all will be fine.

    Finally, you probably know more than you think. You’ve plenty of experience. Most of the time I can do what I need without e.g. classes, but sometimes I’ll intentionally use a technique in a project just to learn it. I can’t learn stuff if I don’t have a use for it.

    I’m still learning, so if I’ve got any part of the above wrong, please help me out.




  • There’s a lot of Scotland, and don’t underestimate driving times. Argyll is good, but can be rather wet any time of the year. Going around now you should be safe from the midgies. Recommend getting onto some of the islands too, and boat rides are always nice. Kerrera is a lovely little island just by Oban. It has a very atmospheric castle, though the teashop isn’t as good as it was so pack a lunch. If you like a dram, make a tour of some distilleries, each has it’s own character. Argyll has lots of archeology & standing stones if that’s your thing. There are loads of lumpy bits of you like walking too. Pretty much anywhere is good, tourist hotspot are ok, but try to get off the beaten track once in a while.

    If you’re driving, and going onto country roads, please please please learn to reverse.

    If you’re lucky you may get to spot some wild haggis, but they’re quite rare now. The farmed ones are cute but have a nasty bite so be careful.

    Also don’t neglect the borders, loads of history.

    It may not sound your thing, but consider geocaching… It takes you to some interesting out of the way places.




  • Arduino and esp32 are both good places to start. On YouTube look up ralph s bacon I think he is - He does lots of microcontroller stuff, and of course the likes of big clive will teach you all about basic electronic circuits.

    If you’re a complete newbie, get a kit and work through the tutorials.

    Stuff you’ll need at first is a microcontroller, prototyping breadboard and a few components (should all come in the kit of you go that route). When you have something that works that you want to keep, you can think about a cheap (ish) soldering station and either veroboard, or look into getting your own boards made.

    A multimeter will help a lot (cheapish will do) and depending on how deep you get, a bench power supply and an oscilloscope, but you can live without those for a while.

    Get good quality solder, and using extra food quality flux changed the game for me. If you are an older person, magnification really helps too!

    Get components in 10’s or more as you’ll save a little and it doesn’t matter much if you let out the magic smoke. For hobby stuff, Alix is your friend.

    Have fun.