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!
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!
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.
Yes prime minister is the most accurate documentary about British politics of all time.
It’s a while since I’ve wild camped so not sure if the status has changed. When I did it was more ‘accepted’ than ‘permitted’. Also, the good spots are closely guarded secrets, so you’re mostly on your own there! I don’t know you’re experience, but for anyone else thinking about wild camping: You want water relatively accessible and depending on the weather, some shelter. (I’ve always drunk from fast flowing streams, never pools and survived without treating the water. You also want seclusion as you really don’t want to be getting any attention from walkers or land owners.
This time of year you won’t be getting much sleep, so decide if you want the evening or morning sun - I prefer the morning sun as it dries any dew off my kit. Looking at the map you should be able to plan a route and spot some quite nice spots if you think about the above. Only spend one night in a location.
I used to leave work early, drive down, get half a walk in, a night camp, finish the walk and be back to work for 9AM. One memorable morning was waking up on top of one of the Carnedds.
My preference was always to bivvi rather than tent as it was easier to carry and far easier to find a hidden spot. - The pleasure, as with most bivvying is generally retrospecive, but great fun. Pitch up at dusk and leave at first light, leave no trace bar some flattened grass and all is good. - Just make sure you pack enough calories and water.
The first wild camp I ever did was on the side of Tryfan in just my sleeping bag on a clump of heather. It would had been perfect if I hadn’t put my hand in goat muck earlier in the evening. - Took two days to wash the stink out.
Happy days. Have fun.
This is very interesting. Have you considered studying social engineering? - I’ve found SE techniques quite understandable to help form a process to deal with people in a ‘useful’ way. Many years ago I was sent on a positive influencing course via work and discovered that most NTs can be quite easily manipulated with a few simple tricks. In the end I stopped using them as it felt unfair.