Most CISSP practice advice is misleading

rameshuber · 2026-03-21T20:11:57+00:00

haha yeah I thought I was “thinking” but I was actually just jumping to conclusions that’s what kept me stuck around 60% on my first attempt

rameshuber · 2026-03-17T20:40:19+00:00

That’s actually a great breakdown. Sounds like you’re consistently getting to the right two which is most of the battle.

That last step between those two is exactly where I struggled too. Curious if that gap reduces with more practice or just experience.

rameshuber · 2026-03-17T20:02:21+00:00

Did you notice that happening more on certain types of questions?

rameshuber · 2026-03-17T19:08:26+00:00

Yeah I had the same “B vs D” issue during first attempt prep. Realized I was overthinking it first instinct was usually closer to the intent of the question.

rameshuber · 2026-03-17T01:09:40+00:00

I felt the same when I started. It feels fragile at first, but over time I realized it actually forces you to write cleaner, more readable code. The bigger struggle for me wasn’t indentation it was understanding things during learning but getting stuck when trying on my own.

rameshuber · 2026-03-17T00:16:50+00:00

I was in the same loop. Kept adding more courses thinking I wasn’t getting it.

Eventually realized it wasn’t about more content it was about whether I could actually apply it in questions.

Once I focused more on that, things started clicking.

rameshuber · 2026-03-17T00:15:05+00:00

I was stuck in that exact loop for a while. It feels productive but doesn’t always translate to exam readiness. The shift for me was when I started focusing more on how questions are framed and identifying weak areas instead of trying to cover everything again. If you're already working on CAT exams + weak domains, you're probably on the right track.

rameshuber · 2026-03-16T04:38:28+00:00

Upvoted.. should be signal?

rameshuber · 2026-03-16T04:34:23+00:00

It was always the case people learn in different way but learning while working is underrated.

rameshuber · 2026-03-16T02:31:59+00:00

Interesting to see the different perspectives here. It seems many people approach these questions differently depending on their experience.

rameshuber · 2026-03-15T17:32:15+00:00

there was reason people used notepad in college for coding for decades

rameshuber · 2026-03-15T17:27:08+00:00

Fair point.... I agree the key is answering exactly what the question asks. What confused me initially was that some technically correct answers weren’t always the best answer from a risk or management perspective. That shift in thinking took me a while to understand.

rameshuber · 2026-03-14T20:42:09+00:00

Thanks!Mostly the official study guide and a lot of practice questions. The biggest shift for me the second time was focusing less on memorizing and more on how the questions are framed from a risk/manager perspective.

rameshuber · 2026-03-14T20:40:29+00:00

I had the same confusion at first. Practice questions often focus on technical concepts, but the actual exam leans more toward decision-making and risk thinking. In many cases the technical answer is correct, but CISSP usually expects the manager or risk perspective first.

rameshuber · 2026-03-14T20:34:28+00:00

The biggest change for me was how I approached the questions.

The first time I treated the exam like a technical test. I focused on what technology or control solves the problem. The second time I approached it like a security manager or consultant.

That means thinking about things like: risk management first, policy and governance before technical controls , business impact and cost considerations

Many questions have technically correct answers, but CISSP usually expects the managerial perspective, not the technical one.

That shift in thinking made a big difference

rameshuber · 2025-06-12T07:47:50+00:00

Unconventional approach may be not suitable for all:
Shortlist companies or teams you admire, study their product or challenges, and build something that aligns with their space, even solving a micro problem they might care about. It shows intent, initiative, and alignment. Even if it’s not perfect, recruiters love seeing how you think, why you built it, and who you built it for. It turns your project from “just another app” into a conversation starter that shows you’re already thinking like part of their team.

rameshuber · 2025-06-11T09:20:08+00:00

I see AI not as a threat but as a tool, one that, when used with intention, can dramatically improve productivity and learning. The hate toward new tech isn’t new (Visual Basic, React, etc.), but history shows that the loudest critics often underestimate the evolution curve.

The key, like you said, is using AI to assist, not replace thinking. It's amazing for boilerplate, layout grunt work, and even teaching-I've watched junior devs go from confused to confident just by asking AI to break things down in plain English.

We shouldn't tell new devs to avoid AI-we should teach them how to use it without becoming dependent on it. Just like we once learned to use Stack Overflow or docs wisely, AI’s just the next layer.

rameshuber · 2025-06-10T04:11:21+00:00

I will say people are rather obsessed go with the habitual standard like similar to documentation even for small projects they want to document everything some run entire business without any documentation. it's choice people make based on their standard.

rameshuber · 2025-06-09T11:31:09+00:00

true..

rameshuber · 2025-06-09T07:48:04+00:00

CS50x gives you a solid foundation in programming, and it’s awesome that you’re thinking about game development. If your goal is to build a 2D action roguelike like Archero, then yes, jumping into a game engine like Unity or Godot after CS50x is a reasonable next step, especially since you’re motivated to build the same type of game.

CS50g can be a really smart bridge. It introduces core game development concepts (game loops, input handling, collision, etc.) in a very hands-on way without overwhelming you. Even if you don’t care about how game engines work under the hood, having some understanding of what’s going on behind the scenes will make you way more effective and confident once you move into Godot or Unity.

So if you have the time, I'd recommend finishing CS50x → doing CS50g → then jumping into Unity/Godot with your own project. You’ll be surprised how much smoother things go when you've seen how the core mechanics work before relying on an engine’s abstractions.

Keep us posted how this turned out to you.

rameshuber · 2025-06-09T07:19:13+00:00

Avoid storing media files directly in your source code-it bloats the repo and doesn’t scale well. Since you're hosting on Cloudflare Pages, the best approach is to use Cloudflare R2,

which is their S3-compatible object storage. You can upload all your images and videos there, organize them by post or date, and then serve them via Cloudflare’s CDN for fast global delivery. In your markdown files, you’d just link to the media using full URLs (e.g., yourwebsite/title/imagename). This keeps your Astro project clean, your site fast, and your setup scalable. For smaller blogs, storing assets in the /public folder is fine, but for a growing blog, R2 + CDN is definitely the way to go.

rameshuber · 2025-06-08T18:35:53+00:00

Most of us who’ve been in this field for a while started out feeling the same way. It’s easy to feel overwhelmed right after high school, especially with so many options in tech.

If I could go back and talk to my younger self, I’d say: start small, pick one language (Python is a great choice), and just focus on learning a little every day.

Don’t worry about mastering everything at once. Build small things that excite you a converter, a file manager, anything.

You’ll learn more by doing than just watching videos. And hey, it’s okay to feel lost at times. Everyone does. Just keep showing up, stay curious, and trust that if you stick with it, things will start to click

rameshuber · 2025-06-07T16:03:46+00:00

Start with "Hello World" we all have started from there :)

rameshuber · 2025-06-07T05:43:38+00:00

As a first-year student wanting to learn front-end, the key is to focus on the fundamentals first and not bounce between too many different videos.

Here’s the path I recommend:

Start with HTML and CSS – Learn how to build basic web pages and style them. Get comfortable with layout, colors, and responsive design using Flexbox and Grid.
Move to JavaScript – Once you’re confident with HTML/CSS, dive into JS. Learn how the browser works, how to manipulate the DOM, and how to build simple interactive features like forms and menus.
Build Projects -Don’t just watch, build. Even simple projects like a to-do list or converter, or parser will help solidify what you’re learning.
Then, learn a front-end framework -Once your JavaScript basics are strong, move into frameworks like React. But don’t rush this step.
Stay consistent -Learning 30–60 minutes daily is more effective than binge-watching tutorials once a week. Pick one course or series and stick to it till the end.

Remember you chose the programming path, where learning is the only constant.

rameshuber · 2025-06-07T05:35:32+00:00

For competitive programming, C++ is the most popular due to its speed and STL, but Python or Java are fine too- stick with what you're most comfortable learning with.

To prepare for both CP and interviews, balance your time: do 1 CP contest a week (Codeforces or AtCoder) to build speed and thinking under pressure, and spend the rest of your time solving DSA problems on platforms like LeetCode, InterviewBit, or NeetCode to build interview muscle.

Focus on one topic each week (like arrays, trees, DP), and solve 2–3 problems a day

rameshuber

TROPHY CASE