DEV Community: Viktoria

5 ASP.NET Mistakes I Wish I Knew Earlier 🚀

Viktoria — Thu, 28 Sep 2023 19:15:09 +0000

Hey Devs! 🙌
ASP.NET is a game-changer, right? But, oh boy, there are some sneaky pitfalls I've (embarrassingly) tumbled into during my journey. Here are a few, just so you can laugh (or cringe) and hopefully avoid them:

😅 "Sure, I trust my users!" Aka Skipping Input Validation
Mistake: Thinking "Who would want to break this?" and letting all inputs slide.
Impact: Hello, Mr. Hacker! 👋 Open doors for vulnerabilities.
Quick Fix: Never, ever trust user input blindly. Client and server-side validation is a must!
🐢 The ViewState Overload
Mistake: ViewState is like that friend who overstays their welcome. Useful but can overburden if unchecked.
Impact: Slow-performing apps. And no one likes waiting, right?
Quick Fix: Don't put everything in the ViewState. Explore alternatives like Session or Cache.
🙈 Ignoring Those Pesky Exceptions
Mistake: "I'll set up exception handling... tomorrow."
Impact: Bugs everywhere and a user experience straight out of a horror movie.
Quick Fix: Always have an exception handling strategy in place. Tomorrow means NOW!
🍝 The Spaghetti of Code + Content
Mistake: Mixing up UI and logic because... shortcuts.
Impact: A maintenance nightmare. Debugging sessions that last for days.
Quick Fix: Keep things tidy. Embrace separation of concerns, and use those code-behind files.
🐌 Sloooooow Database Queries
Mistake: Writing SQL queries on the fly without optimizing them.
Impact: Your app's speed (or lack thereof) can make or break it.
Quick Fix: Avoid SELECT * and get friendly with your ORM. Optimize, optimize, optimize!

Alright, folks! These are my ASP.NET goof-ups. What about you? What ASP.NET blunders have caught you off guard? Drop them in the comments, and let's create a safe space for our dev confessions! 😄👩‍💻👨‍💻

[SQL] Where vs Having?

Viktoria — Thu, 11 Nov 2021 08:38:21 +0000

It is easy to be confused with these 2 clauses because A HAVING clause is like a WHERE clause.
⚠️WHERE clause applies to individual rows and HAVING clause applies only to groups as a whole.

A query can contain both a WHERE clause and a HAVING clause.

✔️The WHERE clause is applied first to the individual rows in the tables or table-valued objects in the Diagram pane. Only the rows that meet the conditions in the WHERE clause are grouped.

✔️The HAVING clause is then applied to the rows in the result set. Only the groups that meet the HAVING conditions appear in the query output. You can apply a HAVING clause only to columns that also appear in the GROUP BY clause or in an aggregate function.

📝As a rule of thumb, use WHERE before GROUP BY and HAVING after GROUP BY. It is a rather primitive rule, but it is useful in more than 90% of the cases.

How to become a successful Software Engineer?

Viktoria — Tue, 09 Nov 2021 18:41:00 +0000

To be honest, I have no idea because my journey is still in progress 😄
But I want to share with you my lifehack on how I increase brain productivity and can do more tasks than previously.

💡All I need is a rest.

😥Previously, I overtired, worked round the clock, and did one middle task full workday. I was so nervous and stressed that it was so hard for me to focus on my duties and get tasks done. Also, I had no idea where can I find time and energy to learn new technologies and master my skills.

🤓Today I turn off my PC after 8 hours of productive work with Pomodoro tracker, have a stroll in the park near my house, go to the swimming pool. Also, I stopped reading the news, set 20 minutes timer on social networks, and spent less time on them. It is unbelievable but I can also find time and energy for English classes, programming courses, and Instagram activities.

Well, perhaps, it sounds so easy to do but it is really hard to win the battle between ambitions and self-care for me.

Stay safe and have a rest ❤️