-- Ambitions 🌌 --
People like to ask the question, "what do you want to be ?" and there are a million ways to answer it. But I choose the one with the shortest letters. "Be", "what ?" you might ask. I will repeat it, "Be". So let me just be.
People like to ask the question, "what do you want to be ?" and there are a million ways to answer it. But I choose the one with the shortest letters. "Be", "what ?" you might ask. I will repeat it, "Be". So let me just be.
🤔3👍1😁1
Make your PC your own Series
This is the series I started to show you guys how you can make your PC more productive and aesthetically pleasing.
1. Your windows
1. Overall feel
2. File Explorer
3. Navigating In Windows
3. Your chromium based browser
4. Your terminal
5. Your IDE
6. Good apps to use
This is the series I started to show you guys how you can make your PC more productive and aesthetically pleasing.
1. Your windows
1. Overall feel
2. File Explorer
3. Navigating In Windows
3. Your chromium based browser
4. Your terminal
5. Your IDE
6. Good apps to use
❤1👍1
You suck at coding, and you don't know why.
Well, here are the 4 most common reasons:
1) You suck at coding because you think you suck at coding. That's right—you don't actually suck at coding; you just think you do. Classic impostor syndrome. Don't ask me why impostor syndrome affects such an obnoxiously high number of software engineers—I don't know—but it does. I've made a video on how to easily combat impostor syndrome, which you can find on YouTube.
2) You suck at coding because you're conflating not knowing everything there is to know about coding with sucking at coding. News flash: nobody can be an expert in every subset of software engineering. Being an advanced backend engineer who's never worked on the frontend (or vice versa) is totally fine and doesn't mean you suck at coding. Similar to reason 1, you don't actually suck at coding here; you're just misinformed.
3) You suck at coding because you don't code enough. Coding is a skill like any other: the more you practice it, the better you become at it. If you're only coding an hour a day, you won't be as good as if you were coding 4 hours a day. If you're only coding 40 hours a week, you won't be as good as if you were coding 60 hours a week. I leave it as an exercise to the reader to determine how much time they want to spend on coding-related activities, since this largely depends on individual life goals.
4) You suck at coding because you're surrounded by people who suck at coding. The saying "you're the average of the five people you spend the most time with" applies just as much to life as it does to coding. If you work at a company that doesn't value technical excellence, or if you're learning coding from someone with bad practices, you're just going to strengthen poor habits (i.e., you're going to suck more and more at coding). Find a place where you're surrounded by great software engineers.
Credit to Clement Mihailescu
Well, here are the 4 most common reasons:
1) You suck at coding because you think you suck at coding. That's right—you don't actually suck at coding; you just think you do. Classic impostor syndrome. Don't ask me why impostor syndrome affects such an obnoxiously high number of software engineers—I don't know—but it does. I've made a video on how to easily combat impostor syndrome, which you can find on YouTube.
2) You suck at coding because you're conflating not knowing everything there is to know about coding with sucking at coding. News flash: nobody can be an expert in every subset of software engineering. Being an advanced backend engineer who's never worked on the frontend (or vice versa) is totally fine and doesn't mean you suck at coding. Similar to reason 1, you don't actually suck at coding here; you're just misinformed.
3) You suck at coding because you don't code enough. Coding is a skill like any other: the more you practice it, the better you become at it. If you're only coding an hour a day, you won't be as good as if you were coding 4 hours a day. If you're only coding 40 hours a week, you won't be as good as if you were coding 60 hours a week. I leave it as an exercise to the reader to determine how much time they want to spend on coding-related activities, since this largely depends on individual life goals.
4) You suck at coding because you're surrounded by people who suck at coding. The saying "you're the average of the five people you spend the most time with" applies just as much to life as it does to coding. If you work at a company that doesn't value technical excellence, or if you're learning coding from someone with bad practices, you're just going to strengthen poor habits (i.e., you're going to suck more and more at coding). Find a place where you're surrounded by great software engineers.
Credit to Clement Mihailescu
🔥6
C - Java - Jav - Ja . .
Did you know that the Java compiler, the very tool that is used to translate Java code into machine-readable instructions, is actually written in...Java itself?! Yes, that's right - the language is so powerful and flexible that it can be used to write its own compiler.
But wait, it gets even more mind-blowing! The process of achieving this self-sufficiency is known as bootstrapping or self-hosting, and involves writing a small, functional version of the compiler in another language, such as C. This initial version is then used to compile a larger version of the compiler that is written in Java. And once this larger version is compiled and functional, it can be used to compile subsequent versions of the compiler, including itself.
In essence, the Java language is capable of creating and sustaining itself, like a self-replicating organism in the digital world. It's a testament to the power and versatility of Java, and a reminder that the possibilities of computer programming are truly endless.
Did you know that the Java compiler, the very tool that is used to translate Java code into machine-readable instructions, is actually written in...Java itself?! Yes, that's right - the language is so powerful and flexible that it can be used to write its own compiler.
But wait, it gets even more mind-blowing! The process of achieving this self-sufficiency is known as bootstrapping or self-hosting, and involves writing a small, functional version of the compiler in another language, such as C. This initial version is then used to compile a larger version of the compiler that is written in Java. And once this larger version is compiled and functional, it can be used to compile subsequent versions of the compiler, including itself.
In essence, the Java language is capable of creating and sustaining itself, like a self-replicating organism in the digital world. It's a testament to the power and versatility of Java, and a reminder that the possibilities of computer programming are truly endless.
😱6🤡1👨💻1
The urge to simply wait for the single scheduled event of the day to start and do nothing else in the meantime ☹️ !!
Basic 7 days long *Learn Complete Python And Artificial Intelligence*
*No Prerequisite required*
*You will learn:*
1). Introduction to python
2). What is AI
3). Algorithms in AI
4). Create an AI that can play tic tac toe
*Certificates are provided by DevTown , Google and Microsoft at the end for free*
*REGISTER NOW:!!*
https://forms.gle/WQhtz5iWcJ9EAK3j8
*Join the WhatsApp community*
https://chat.whatsapp.com/LhddcqrGmt72pJBs7ZIoaK
*No Prerequisite required*
*You will learn:*
1). Introduction to python
2). What is AI
3). Algorithms in AI
4). Create an AI that can play tic tac toe
*Certificates are provided by DevTown , Google and Microsoft at the end for free*
*REGISTER NOW:!!*
https://forms.gle/WQhtz5iWcJ9EAK3j8
*Join the WhatsApp community*
https://chat.whatsapp.com/LhddcqrGmt72pJBs7ZIoaK
👍1
This media is not supported in your browser
VIEW IN TELEGRAM
-- Meme of the day --
My first AI project !!
My first AI project !!
🤣5😁3
If you are starting flutter, check this out. It can be a good starting point.
https://github.com/dagimg-dot/Counter-On-Steroid
https://github.com/dagimg-dot/Counter-On-Steroid
GitHub
GitHub - dagimg-dot/Counter-On-Steroid: Simple Counter with some surprises built using flutter.
Simple Counter with some surprises built using flutter. - GitHub - dagimg-dot/Counter-On-Steroid: Simple Counter with some surprises built using flutter.
Just open-sourced what we worked on for a month for our Advanced Programming in Java course. Even if the feedback we got was not satisfying we learned a lot from it and we are really proud of it.
It is a Resident ID Issuing System implemented using JavaFX and SQLite.
Check it out on github
It is a Resident ID Issuing System implemented using JavaFX and SQLite.
Check it out on github
🔥9👏1