RandomUser

joined 1 year ago
[–] [email protected] 3 points 6 months ago

Thought I did so well on my phone. It kept auto correcting code to coffee. Maybe it was telling me something.

Yes, plan for it!

[–] [email protected] 5 points 6 months ago (2 children)

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.

[–] [email protected] 12 points 7 months ago (1 children)

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.

[–] [email protected] 26 points 9 months ago (1 children)

3 day working week will more likely mean companies cutting staff by 50%. Can't imagine most people being able to live when only working 3 days.

[–] [email protected] 36 points 10 months ago (1 children)

Why wasn't there security on the device? My works devices are password protected and it's a disciplinary offence if I share passwords or give unauthorized access.

If he gave them the login creds, then he should be penalised .

If he logged in and gave the device to non parliamentary staff, he should also be penalised.

He got caught because it cost money, which is the lesser offence. Cyber security should be more robust for ministers than it is for most companies, but seemingly not.

[–] [email protected] 0 points 1 year ago

Not sure if this vid will help you, but it's real life experience of carrying for someone who has the disease.

https://youtu.be/jRltbhRO-sY

Apparently other people have said it's accurate and helps. I've no connection other than following the creator for his excellent technical content.

[–] [email protected] 14 points 1 year ago

The PI is always a good place to start, but they're not cheap anymore. You can still do some useful things at the command line (not sure how fun, but a great education), python is there and very accessible. - get a camera and you could do some great things with open CV. Not sure what packages are out there though. Think you'd just have to follow some web tutorials.

As an alternative, have you considered an Arduino kit? Lots of great projects, all very well documented. Playing with LEDs, sensors, motors etc may keep their attention longer than a bash prompt.