eHalum

03/02/2024

27/01/2024

What is code freeze in the software engineering field?

Code freeze in the software engineering field refers to a specific phase in the software development lifecycle during which no new code is allowed to be introduced or modified in the software project. This period is typically implemented to stabilize the codebase and prepare for a release. The goal of a code freeze is to ensure that the software is in a reliable and consistent state, minimizing the risk of introducing new bugs or issues just before a scheduled release.

During a code freeze, developers focus on addressing and fixing existing issues, such as bugs and critical issues, rather than adding new features or making significant changes to the code. This helps create a stable release candidate that can undergo thorough testing and validation.

Code freezes are common before important milestones, such as major software releases, product launches, or customer demonstrations. They provide a clear point in time where the codebase is considered "frozen" for new feature development, allowing the development team to concentrate on quality assurance and ensuring that the software meets the desired level of stability.

Once the testing and validation processes are completed successfully, and any identified issues are addressed, the code freeze is lifted, and the software can proceed to the next phase of the development lifecycle, such as deployment or distribution to end-users.

09/12/2023

That is a serious crime.

10/11/2022

Look at that colorful contest floor! 👀🎈The 45th ICPC World Finals in Dhaka, Bangladesh is in the final hour!

24/09/2022

13 Sites to Get FREE Stock Photos for coders

✅ Nappy .co
✅ Pexels .com
✅ Reshot .com
✅ Freepik .com
✅ Pixabay .com
✅ Stocksnap .io
✅ Picspree .com
✅ Stockvault .net
✅ Picography .co
✅ Picjumbo .com
✅ Unsplash .com
✅ Pikwizard .com
✅ Gratisography .com

29/08/2022

23/08/2022

Common CSS Mistakes every Developer should avoid🎨

1️⃣ Using px
Px locks your design to a fixed size for all screens.

You should always try to use relative measurements such as em, rem, %, etc and wherever possible.

2️⃣ Using one CSS file for styling
Using single file in big projects can create mess.

Try to use different CSS files for different components.
For example: Create 2 different CSS files for navbar and footer. This will also increase the reusability of code.

3️⃣ Using inline CSS
You have to write the same code again & again for different elements, there is no place to put these styles for reuse.

Since there is no specific location for code, editing inline CSS is a task!

Always try to use external stylesheets until needed.

4️⃣ Using !important everywhere
The only thing that can override an !important is another !important, and once you go down that road, it never stops.

There's no point in jamming your CSS with a lot of !important styles and become gridlocked.

5️⃣ Not using proper naming convention
Make sure to name classes, ids and other attributes properly and in a similar manner.

Try storing color values in variables instead of copying same color over and over again.

6️⃣ Not designing beforehand
It feels amazing to just start building without thinking much, but this can turn in a mistake once things get complex.

Try to have a clear picture of project. It'll also reduce the chances of redundancy.

7️⃣Being too creative
Tbh, you don't need heavy CSS or animations forced into your website. Elegant design with good UX/UI is preferred by everyone.

Don't try showing all your skills in one project only.