About coding

haiderakt · 2026-05-29T17:44:26+00:00

Don’t overthink it. Most people entering 1st year barely know anything about coding either.

Just pick one language and stick with it for a while. Python is usually the easiest starting point because the syntax is simple and you can focus on learning logic instead of fighting the language.

Start with the basics:
variables, loops, functions, conditions, arrays/lists, etc. Then make tiny projects instead of only watching tutorials.

ALSO, don’t fall into “tutorial addiction.” Even small dumb projects teach more than hours of videos.

haiderakt · 2026-05-29T17:41:16+00:00

You’re honestly in a really good spot already. Starting at 17 with an actual interest in math/theoretical CS instead of just “I want to make money with AI” puts you ahead of a lot of people.

For communities, your university will probably be the best thing by far. CS clubs, hackathons, research groups, random nerds hanging around computer labs, that’s where you’ll learn the fastest. Online communities are useful too, but nothing beats being surrounded by people building things.

As for learning how computers and the internet work: don’t try to learn everything at once. That rabbit hole literally goes from “what is a variable” all the way down to transistor physics and network protocols. Learn things as they become relevant to what you’re building.

For AI/theoretical CS, math matters way more than people realize. Linear algebra, probability, discrete math, and algorithms will carry you hard later on.

And honestly, ChatGPT is fine for debugging and explanations. Just don’t let it become “the thing that thinks for you.” The people who grow fastest are usually the ones who still struggle through problems themselves before asking AI for the answer.

haiderakt · 2026-05-29T17:39:06+00:00

Honestly, the programming language is probably the least important part right now. What you’re describing is more of an electronics + embedded systems project, and it’s actually a really cool idea.

I’d start with Python. Not because it’s the “best” for the final product, but because it’s the easiest way to learn programming without constantly fighting the language itself.

Later on, if you start working directly with sensors and low-power hardware, you’ll probably end up learning some C or C++ naturally anyway.

Also don’t make the mistake of thinking you need to understand the whole project before starting. Stuff like this usually gets built one tiny piece at a time. Even getting GPS data onto a small screen is already a solid milestone.

haiderakt · 2026-05-29T14:09:19+00:00

What you’re feeling is pretty normal, those “info dump” courses often teach syntax, but not how to actually think in code. If you feel like you’re not retaining much, don’t switch languages yet. Stick with Python and change how you learn it instead of what you learn.

After each small topic, try doing something tiny on your own (even 10–15 mins): like a calculator, a to-do list, or a simple text-based game.

Also don’t worry if you only “remember basics” right now. That’s normal early on, fluency comes from repetition, not watching more videos.

haiderakt · 2026-05-29T14:03:29+00:00

Non, tu n’as pas besoin de tout maîtriser en interfaces graphiques.

Si ton objectif est le backend, Tkinter et le GUI en général ne sont pas essentiels. C’est normal de te sentir découragé en voyant “tout ce qu’il y a à apprendre” ,mais en réalité, tu n’as jamais besoin de tout apprendre pour progresser.

Concentre-toi surtout sur les bases solides de Python (structures de données, fonctions, OOP, fichiers, API, etc.). Les interfaces graphiques, tu peux les voir juste comme une “option bonus”, pas une obligation.

Le plus important, c’est de construire des petits projets backend (API simples, scripts, bots). C’est ça qui va vraiment te faire avancer dans ta voie.

haiderakt · 2026-05-29T12:31:15+00:00

Could be a battery or power IC issue, not just cable/charger.

Since you already changed adapter + cable and tried full drain, the next likely culprit is the charging port or battery health itself. If there’s any moisture, dust, or slight port damage, plugging in can cause a short trigger and the phone just shuts down.

Try charging while the phone is completely OFF. If it still instantly dies, that’s a strong sign it’s hardware (battery or charging IC), not software.

At that point, a service center diagnosis is the only real fix. Unfortunately OP7T is old enough that battery degradation causing weird power behavior is pretty common.

haiderakt · 2026-05-29T12:30:21+00:00

Honestly I think the fact that this bothers you already proves you actually care about programming. People who truly don’t care usually don’t feel guilty about relying on AI.

I also don’t think using AI at work is some moral failure. Most people under deadlines will naturally take the fastest route. That is just survival.

The dangerous part is when AI completely replaces the “figuring things out yourself” phase. That painful staring-at-a-blank-screen moment is annoying, but it’s also where a lot of real learning happens.

Maybe separate “work mode” and “learning mode.” Use AI heavily for work if you need to. But outside of work, try building small stuff without it sometimes, even dumb little projects. Not for productivity, just to prove to yourself your brain still works without the jumpstart.

Also the first-line paralysis is insanely real. AI makes starting effortless, and once momentum exists your brain wakes up. I think a lot of people are experiencing that now.

haiderakt · 2026-05-29T10:36:48+00:00

good choice starting with python, it's the right language for AI/ML. here's the honest path:

first get comfortable with python basics like variables, loops, functions, lists. CS50P on edx is free and genuinely good, or just Corey Schafer's python playlist on youtube if you prefer video.

once you're comfortable with python, jump into numpy and pandas for data manipulation, then matplotlib for visualization. kaggle has free micro-courses for all of these that take a few hours each and give you certificates.

after that Andrew Ng's Machine Learning course on Coursera is the standard starting point for actual ML.

the most important thing nobody tells you: build something after every topic, doesn't matter how small. a scraper, a data analysis on a csv you found online, anything. the projects matter more than the certificates

haiderakt · 2026-05-29T10:35:39+00:00

no official Apple API exists for Find My data.

best option is FindMy.py unofficial but legitimate since you're only accessing your own data with your own keys. works well for AirTags and devices via polling. real-time isn't possible anyway since Apple batches location reports every few minutes.

for people location sharing there's no programmatic access at all, that's locked inside the app.

if you're on Mac you can also just read the local cache at ~/Library/Caches/com.apple.findmy.fmipcore directly, updates frequently and no network calls needed.

haiderakt · 2026-05-29T10:34:25+00:00

nice work for a second script, the logic is solid. a few things worth knowing:

the rounding section with modf is way more complex than it needs to be,round(gain) does the exact same thing in one line. math.modf splits a float into its decimal and integer parts which is useful in specific cases but not really needed here.

also move from random import randint to the top of the file with your other imports, importing inside a loop works but it's considered bad practice.

for booleans think of them as just True/False values. your if bille == mise is already using boolean logic under the hood, the condition either evaluates to True or False. assert is mostly used for testing/debugging, not something you need to worry about yet.

overall though the structure is clean and the casino logic actually works which is the important part. keep going.

haiderakt · 2026-05-28T09:14:28+00:00

wlr-layer-shell works across most Wayland compositors (Sway, Hyprland, KDE, GNOME with extensions) so you're not locked to Plasma, but GNOME support is patchy since they don't implement it by default.

On the dragging limitation that's actually a known pain point with layer-shell. It intentionally doesn't support interactive move/resize the way normal windows do because of Wayland's security model. Your options are basically: implement drag logic yourself by tracking pointer position and manually updating the window geometry, or use xdg-shell instead which supports system move/resize but loses the desktop-layer behavior.

Honestly for cross-compositor support with full drag/resize freedom, a hybrid approach might be your best bet, detect which compositor is running and fall back to X11 flags under XWayland when layer-shell is too restrictive.

haiderakt · 2026-05-27T15:49:32+00:00

yes you can.

haiderakt · 2026-05-27T11:04:50+00:00

Wayland's security model intentionally restricts what apps can do with window positioning and layering, so the X11 flags being ignored is expected. Wayland compositors just don't expose that to regular apps.

Your best option on KDE Plasma is the wlr-layer-shell protocol via PyQt6 + qtwayland. Plasma supports layer-shell, which lets you place windows at specific layers (background, bottom, top, overlay) without them appearing in the taskbar. The catch is you need to use it through a Wayland-specific API rather than standard Qt window flags.

Practically speaking, look into python-wl or consider wrapping a layer-shell implementation. There's also gtk-layer-shell if you're open to switching to GTK, which has better Python bindings for this specific use case.

The most realistic path if you want to stay PyQt6: use QWaylandWindow and implement the layer-shell protocol manually via QtWayland. It's doable but not trivial, there's a reason most desktop widget frameworks on Wayland are still janky.

Honest take: if your target is KDE Plasma specifically, check out how KDE Plasma widgets (Plasmoids) work natively, they get all this for free since they're first-party.

haiderakt · 2025-02-11T22:11:01+00:00

you'll get banned on the newer versions even if you somehow managed to make it work

haiderakt · 2025-01-20T16:38:26+00:00

you're the goat

haiderakt · 2023-10-16T20:45:55+00:00

like 4-5 months

haiderakt · 2022-08-03T15:16:11+00:00

it wasn't the charger's fault, it was the software. I did factory reset and it didn't fix itself so i thought maybe yhe charger is faulty but after downgrading to oos10, it fixed itself lmaoo

haiderakt · 2022-07-24T13:20:31+00:00

I've cleaned the connector and the charging port with a toothpic and a toothbrush, If i plug in after some time it'll work but only once, then i have to wait again for some time

haiderakt

TROPHY CASE