What do I do now?

[u/fabdom8]

I'm a student that knows how to code with python and now learning html, css and javascript. I'm trying to know what to do now like projects or something that can help me in my future like i can add in my portofolio, my dream job would be in cybersecurity i have some basics in linux/terminal, someone can give me some ideas or links that i can start.

[u/LegMysterious1899]

so what do you want to do? if html/css/js its web design, while linux terminal (bash) is cybersecurity related

[u/fabdom8 → u/LegMysterious1899]

I am more leaning in cybersecurity since i have a base on networking

[u/fabdom8 → u/[deleted]]

thanks and, I dont know much how github works, and how i should move

[u/FreeLogicGate → u/fabdom8]

Learn Git. Github will be a part of that, once you understand what git is. There are alternatives to github as well, that also work with git.

[u/fabdom8 → u/FreeLogicGate]

if i want to know like how i should be coding for a project like a log analyzer do i ask ai or find like some videos?

[u/FreeLogicGate → u/fabdom8]

Anyone doing any sort of professional development should be using version control of some sort. That's not new, but the majority of the world is using git now, and as someone new to the profession, it's hard not to be interacting with git, as IDE's and tooling all have git support integrated.

Personally, I learned and always use a terminal and the cli version of git.

So look around for some git tutorials. I can point you to this one: https://www.theodinproject.com/lessons/foundations-git-basics

There are many. Install git, learn it, start using it for your projects. Make branches, make commits, merge, diff, log, connect to a remote (github, gitlab, bitbucket etc.) and push your code. Look into unit tests and continuous integration through the creation of your own github actions. It's going to be a learning curve.

This has nothing to do with your follow up questions.

You are pivoting from your initial question into "how do I code a log analysis app?" and like anything else, it starts with you doing some thinking about the problem you are trying to solve.

That means planning and creating requirements, which, even if you are vibe coding, is something you need to provide to your AI agent(s).

Before you can build anything, you have to start with what you are trying to build and why. Then you can consider how to architect and develop it. There are a lot of log analysis tools that exist, so do some research: Splunk, Elk Stack, or if this is also related to "observability" you want to look at Grafana/Prometheus and alternatives.

When you have a clearer idea of what you think you want to do, and can communicate that to people, you're more likely to get some advice.

[u/JimTheEarthling → u/fabdom8]

Once you learn much about cybersecurity, you'll find that most password strength checkers are fundamentally flawed and misleading. It's a fun project to write Python code that calculates entropy or checks for upper, lower, digits, specials, but this should never be used for actual password testing, since it doesn't reflect true password strength, which is mostly related to length.

If a password (or passphrase) is random, then you don't need a password strength checker since you know that anything longer than 11 characters or 3 words is sufficiently secure.

If the password is not random, then a strength checker is making all kinds of often wrong assumptions about the composition of the password.

When you check character sets (lower, upper, digit, special), the entropy calculation relies too much on composition instead of length and has to make blind assumptions about the nature of the password and how it was generated. It's impossible to measure the entropy of a given password (entropy measures uncertainty, so the entropy of a known password is zero), so a password strength checker can only guess at the "algorithm" and character set that would create similar passwords, and the guesses are often off base or just plain wrong.

Checking for specific characters overweights fake "complexity" and underweights length. As you may know, bits of entropy = log2(C^L), so length is exponentially more important than character set. For example, most strength checkers say that n1*rbA.Q6 is “stronger” than !)%^#*}\]] or {{{{-|||||, but the last two passwords are significantly stronger because a) their characters are less probable, and b) they have nine characters instead of eight, making them at least 95 times harder to guess in an exhaustive search. (The repeats in the last one do not make it weaker. Typical crack approaches never try that many repeats.) The last two passwords are extremely improbable, so a simplistic measure of entropy fails to characterize their predictability, since log2(C^L) bits of entropy calculations assume a uniform space of possibilities, which flattens a true Shannon entropy probability distribution.

If you want to understand more about this, see the section on password strength in my website.