This seems <i>really</i> obvious, but I'm glad someone is saying it. I think there's a trend of "Teach everyone to code" like a vocational thing that misses the extent to which coding is <i>nothing like</i> e.g. plumbing. As in, with plumbing, the <i>best way to do things</i> is much more generally known and teachable.
Just don't be a cheap date. I'm hardly any kind of "hacker". I'm barely a "programmer".<p>But if I'm in a conference room, and I see some little embedded computer powering something, my mind immediately starts going "Oooo, wut that? Does it run something unixy? I wonder if it connects to the same network as the main office. I could probably borrow its little flash memory disk without anyone noticing for a day or so. I bet I could put a program to open a reverse shell for me so that I can just peacefully chill behind the firewall anytime I want."<p>Etc, etc etc. I can't help it. I'm curious! I'm also not very driven and highly nervous. But what if I were driven and brazen, but also very curious?<p>Put important things behind a firewall, and make sure that firewall is correlated to a physically secure location. Password protect systems that need protection. Encrypt things that are critical and confidential. Limit the number of people who have unrestricted access. Divide your network so that more public services only communicate with more secure backend service as little and as securely as possible. Don't hire people you don't trust. Compensate the people you hire well. Be ethical so that people generally won't delight in your downfall.<p>And then live your life! Lol.
> Programming is a complex task that includes five steps: problem identification, solution design, coding, testing and reporting.<p>Perhaps it's because of different terminology, but I'm already somewhat lost on the first sentence of the article. What does reporting mean in this context?
In principle yes, but the objectives (constructive/destructive) produce different satisfaction. A programmer on a sizable team might not have the same commitment as one on a smaller team. He/she may think so, but it’s almost always, not the case.<p>I’m speaking from experience.
is this a listicle? i don't really understand what the purpose of this article is. What makes hackers mindset useful to programmers? what makes these points the valuable takeaways. Not asking hn, it just seems missing from the article
This article missis its own opportunity.<p>Most of what this article talk about can be learned in a couple of days. Get familiar with ZAP, a proxy to replay and modify http request useful to test webapps for things like XSS, sql injections, Maltego, a fancy port and networks scanner, and some other tools you or a 12 year old can learn from youtube.<p>Seriously this hacking things is overrated and shift-left-security is a joke with the same punchline as DevOps, more best practices mandated by consultant that don't do the actual work, for engineers to follow instead of giving them the space to think about a good problem/solution fit.