Daniele Cangi’s DEV Community post “I Never Planned to Work in Cybersecurity” (dated Sep. 30) is written before the story it points to. He is about to enter a cybersecurity environment and does not claim to know the field yet. It is not a success story. The post doesn’t say what role he ended up doing or whether his scattered background helped. What it offers is a plan for the first stretch: find out what is actually there, and keep careful track of how you know it.
What Cangi says about his background
Cangi describes work across procedural systems, AI experiments, GPU computing, RF observation, benchmarks, games and developer tools. He says he usually begins with a problem he wants to understand or an idea worth testing, not with a career plan, and that no single plan has tied these projects together. The title follows from that: cybersecurity was not a destination he aimed at.
As an Amazon Associate I earn from qualifying purchases.
He does not say this breadth qualifies him. He treats it as an open question whether the habits from those projects carry over to security work, and he says he intends to examine that over time. That restraint is the most useful thing in the post, because the usual version of this story assumes the answer is yes.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchHis first task: understand what is already there
A new project can be built to your own design. A new organization cannot. Cangi points out that its systems and constraints already exist, and that colleagues carry knowledge that may never have been written down. So his stated first job is to understand what is actually there: the systems, the limits on them, the people, and the unwritten context.
#1 Best Overall
This is a sound default for anyone joining an established environment. Before proposing changes, find out which things are deliberate, which are accidents of history, and which only someone who has been there for years can explain.
Keeping sources of knowledge separate
The post’s clearest practical idea is epistemic discipline. Cangi wants to keep five kinds of knowledge apart, and the list works as a note-taking habit for any newcomer.
| Kind of knowledge | What it means in practice |
|---|---|
| Directly observed | Something you saw or checked yourself |
| Expert input | What domain specialists tell you |
| Documentation | What written material says, which may be stale or incomplete |
| Inference | Your own reasoning from the above; a hypothesis, not a finding |
| AI-supplied | Output from an AI system, which may be plausible without being correct |
Why the AI row matters most
Cangi notes that AI can make an unfamiliar person sound informed quickly. The risk he names is confusing plausible language with actual understanding. Fluent explanations arrive before the learner can judge them. In a security setting, where a confident but wrong statement about a system can mislead other people, labelling each claim by source is a cheap safeguard. A practical version is to tag notes as observed, told, documented, inferred or AI-suggested, and to move an item up the list only after it has been checked.
What the post does not establish
- It makes no claim that Cangi has cybersecurity expertise.
- It does not predict that generalist skills will transfer. That is a question he plans to examine.
- It does not say what role he ended up in or how the move turned out.
- It does not offer a recipe for entering the field.
Read it as a baseline: a statement of what one person knows and doesn’t know at the start, with a method for learning the rest.
Rank #3
Wider context: there is no single route in
Cangi’s account is one case. Other sources make the broader point, and they should be kept distinct from his story.
Wiley’s career-path guidance
An excerpt from the 2021 Wiley book Navigating the Cybersecurity Career Path says: “There is no right path for a security career.” It lists routes such as school, certification, internship, learning on the job, or moving over from adjacent work. It also recommends reflecting on your strengths, values and fit for a role. The opened passage does not name the author of the career story around that sentence, so the line is best treated as the book’s general advice. The excerpt also recommends Tribe of Hackers: Cybersecurity Advice from the Best Hackers in the World as practitioner perspective for people entering the field; it is optional reading.
| Route | Where it tends to help | Question to ask yourself |
|---|---|---|
| School | Structured foundations and formal credentials | Do I need a formal base, and can I commit the time? |
| Certification | A defined syllabus and a recognizable signal | Does it fit the role I’m aiming for? |
| Internship | Hands-on exposure with support | Is one available to me at this stage? |
| Learning on the job | Real systems and real constraints | Is there someone who can show me what isn’t written down? |
| Adjacent work | Reuse of existing skills | Which of my skills transfer, and which only seem to? |
The excerpt presents these as alternatives and does not rank them. The “where it tends to help” column is a general reading, not a claim from the excerpt about any route’s outcomes.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Noopur Davis: another unplanned path
A SecurityWeek interview by Kevin Townsend describes Noopur Davis’s move from software development into cybersecurity leadership. It is a second example of a career that did not follow a plan. It is a different person’s story and says nothing about Cangi’s outcome.
Quick Recap
Best Value
What to take from it if you’re in a similar spot
- Say plainly that you are new. Cangi frames the move as entering an unfamiliar environment, not as proof of mastery.
- Treat transferability as something to test. Broad experience may help, but the post doesn’t assume it will.
- Begin by mapping what exists: systems, constraints, people, and knowledge that lives only in colleagues’ heads.
- Record where each belief came from, and be most careful with fluent AI answers you can’t yet judge.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
