u/LegitimateBoy6042

I just cleared the AWS Certified Cloud Practitioner (CLF-C02) exam and wanted to share something that really helped me during my prep, my personal notes.

I’ve had around a year of hands-on experience with core AWS services like EC2, S3, IAM, and Lambda, which made understanding the concepts much easier.

For this exam, I prepared for about 4–5 days, following Stephane Mareek’s course and practicing with some free tests I found online.

These notes summarize the key services, concepts, and use cases in a way that I found easy to understand and remember. While they were super helpful for me, I’d recommend using them.

Doing practice exams is also really important to get comfortable with the question format.

You can check out my notes here : Notes

Good luck to everyone preparing for the exam !

Final phase of BTech CSE student here from a Tier-2 college. Did an internship at an MNC and landed a decent 2-digit placement offer recently. Can’t share much more than that.

Also before people start saying “AI generated post”, I only used AI to clean grammar and structure. Whatever is written below is completely from my own experiences and observations over the last 4 years. Not AI slop.

And these are just my personal opinions, not facts. You might disagree with some things and that’s completely okay.

One thing I genuinely want to tell juniors is, please don’t enter engineering with the mindset that “sab automatically ho jayega”. I saw a lot of people in first year being extremely chill about everything. Like life is sorted already and somehow things will work out on their own. Please don’t have that mindset. I’m not saying live in fear or stop enjoying life, but engineering rewards people who start early and stay consistent. The people who are too relaxed initially usually suffer later when they realize competition is real, they are already far behind.

Your first year matters much more than people think. Not because every subject might not be related to your branch, but because it builds discipline and consistency. It also helps your CGPA a lot. And honestly, I know many people nowadays say CGPA doesn’t matter, but I personally feel it does matter in some ways. CGPA does not represent intelligence, but it does represent the effort you are willing to put in. It slowly builds your reputation in college too. When people hear someone has a 9+ CGPA, they naturally take that person more seriously. Even faculty members tend to trust such students more during difficult situations. At least try maintaining 8+ if possible.

Another thing I noticed is that many students do put effort, but in completely random directions. They keep jumping from one thing to another without understanding why they are doing it. Engineering is already very fast paced, so effort without direction usually takes you nowhere. Spend more time strengthening your weak areas instead of only doing comfortable things. Reach out to professors if you have doubts. Honestly, most faculty members are actually helpful if you genuinely approach them properly.

And this brings me to another important point, never be arrogant. Not with professors, not with lab staff, not with coordinators, not with anyone. Build good relations with people in college. Help them when you can, communicate respectfully, and stay approachable. You may not realize the benefit immediately, but during some serious issue later in your BTech journey, these relationships suddenly matter a lot. Sometimes one supportive faculty member can solve problems that would otherwise become huge headaches.

Also please stop normalizing studying one night before exams. Yes, sometimes it helps you pass, but it doesn’t make you knowledgeable. I’m not saying study daily for hours, but at least pay attention in lectures and understand things slowly throughout the semester. Then exams become much easier and far less stressful.

Now coming to projects, this is something I feel strongly about. In CSE especially, many students simply take projects from GitHub, change the UI a little, and submit them. Maybe it gives marks, but it destroys actual learning. Later during vivas and interviews, they struggle badly because they never truly built anything themselves. Try building useful projects around real ideas, even if they are small. One mindset that helped me was thinking “project to product”. Build something in a way that feels useful to actual people. Instead of taking projects from GitHub, try making projects that someone else would want to take from your GitHub.

And don’t just make one or two projects during your whole degree. Build multiple things. Good projects give you actual exposure, real debugging experience, and important discussion points during interviews.

Communication skills are another thing students ignore for way too long. Many technically strong students later suffer badly when they see someone less technically competent getting better opportunities, and then they blame everything completely on luck. Luck is definitely a factor, I agree with that, but communication matters a LOT more than people realize. If you cannot explain your thoughts confidently, present properly, or communicate naturally, it affects interviews heavily.

If you’re not naturally good at communication, that’s okay. This is exactly the time to improve. During presentations, stop reading directly from slides and actually try presenting. People may laugh for one day, but they forget the next day anyway. Your improvement stays with you forever.

Hackathons are another thing I have mixed opinions about. They are honestly great till second year because they teach teamwork, pressure handling, networking, and fast learning. But personally I feel that from third year onwards, unless there’s PPO or internship potential involved, spending excessive time on random hackathons is usually not worth it. At that stage, placements should become the priority. Because in interviews, hackathon certificates alone won’t save you. You still need strong fundamentals, projects, communication, and preparation.

Your peer group also matters much more than people think. The people around you slowly shape your mindset, habits, and discipline. Try staying around ambitious and hardworking people. Especially for projects and placements, having a strong team where everyone contributes properly saves you from massive headaches.

And yes, enjoy events, sports, clubs, gatherings, all of that. College life should not become robotic. But always remember those things are side activities, not the main track. Don’t get so lost in them that you forget your actual priorities.

One personal rule I always followed was this, if I cannot openly tell my parents about something, I should probably avoid doing it. This may not apply to everyone because every family is different, but personally I feel this mindset saves people from many unnecessary problems.

Another thing engineering taught me is that compounding effect is very real. A lot of students suddenly wake up during placement season, but placements are mostly the result of your previous few years of effort. CGPA, projects, communication, networking, internships, consistency, everything compounds slowly.

And yes, luck absolutely exists too. Sometimes you’ll see technically weaker people getting better opportunities. Don’t destroy your mental peace over that. Stay stable, keep preparing, and stay in the game. Your time comes too.

Finally, try thinking long term before making decisions. Even small things. Engineering teaches you many things beyond coding. For me, one of the biggest lessons was learning how to think strategically about effort and time.

That’s pretty much what I wanted to say. Maybe some people will disagree with parts of this, and that’s completely okay.

All the best to everyone currently surviving engineering :)

The Windows clipboard has been giving me trouble for months now.

I use clipboard constantly while coding, writing docs, sharing links, using commands, and switching between different apps all day. But after using the Windows clipboard for a long time, I realized it still missed many things I needed in my workflow. Clipboard history disappearing after restart, no proper search, no way to save important clips for long-term use, and overall it never felt built for heavy daily usage.

So I decided to build something for myself.

The project is called ClipStack, a lightweight clipboard manager for Windows built with Tauri + React. I’ve been using it daily for the past few days and honestly it has already become part of my workflow.

One thing I cared a lot about while building it was keeping it fast and lightweight. That’s why I chose Tauri instead of Electron. I had previous experience with Electron and it’s great, but for a utility app like this I wanted something that feels more native, responsive, and efficient. Since Tauri uses Rust under the hood, the app feels extremely smooth while still staying under 15 MB.

The app is fully local-first. Everything stays on your machine with local SQLite storage, so there’s no cloud sync or external upload happening in the background. You get persistent clipboard history, fuzzy search, pinned clips, reusable snippets, quick paste workflow, export support, and a keyboard-first overlay that opens instantly with Alt + V.

The goal was simple, make something that stays out of the way but becomes super useful once you start using it daily.

Would genuinely love feedback from people who use clipboard managers regularly or anyone interested in lightweight desktop apps.

Download

More info and screenshots

I recently built a small side project - a desktop app that can download videos from most sites (basically anything supported by yt-dlp).

I started this because I was tired of using command line tools every time, and most GUI apps I tried felt either outdated or unreliable. So this was mainly a learning + personal use project at first, but I kept improving it over time.

It now has a clean, minimal UI and is structured more like a proper app with sections for download, queue, history, and settings. I tried to keep things simple but still useful.

It supports queue downloads, pause/resume, playlist downloads, and lets you pick quality or format. Along with that, I’ve added a few things that made it much more practical to use:

• Clipboard watcher for quick link detection
• Clip range download (download only a part of a video)
• Better logs and queue handling
• Smart fallback when downloads fail
• Auth/cookie support for restricted videos
• Built-in updater for yt-dlp and the app

Also made it cross-platform now (Windows, macOS, Linux), earlier it was just Windows.

If anyone wants to try it: Just download the setup from Releases and run it.