Today I learned how to inspect hard to get elements in the DOM using a CSS trick in the console.
So what you basically do is that you go into the console, you set a delay timer and then run the debugger. Before the debugger starts you open the elements that e.g in my case it was a dropdown
The command is setTimeout(() => {debugger;},3000)
This just freezes the DOM, it currently works for Chrome, it should also work on other browsers
Writing seems to be something that takes less effort, it seems more like a natural extension of my thoughts. The more I write, the sharper my blade seems to become. therefore i would like to write for a greater audience, and so Im moving to medium, where things can be found.
Should I or should I not. I will think about it and make a decision in a week
What I learned today in SE is that there are a ton of tools out there like Cypress for Web application testing, and Espresso for Android Application testing, there is also appium which is a cross-platform testing framework meaning that we can use it to write test cases for all sorts of application, IOS - Android -Web and Desktop
When I was learning how to become a software dev, it was overwhelming to see the number of tools and technologies that people would mention on their CV but it helps to focus on what you want to build and learn that rather than learn everything around it
Thats my advice for today
Things I can do better:
Spend more time on building - e.g 7:4:1 Ratio of building : learning new things/things realted to what im building/analyzing how what I built can be improved
Software Design Patterns are ways of writing software, they can be divided into these types, each with their own advantages and disadvantages, need to get into these more - tbc
Erfahen Sie Mehr Uber Pakete
Ich habe vor kurzem angefangen, an einem projekt zu arbeiten es verwendet MERN.
Learning about Packages
I recently started working on creating a react app, in the MERN stack and I was confused about the packages.json file
Turns out that it was basically something that kept a track of the dependencies/tools that we need to use to make sure that our application is working correctly
React uses a declarative approach for making programs, for example, in an imperative flow, we tell the computer exactly how to manipulate the DOM (Document Object Model)
[ Also look at, what is a DOM?]
We specify where the control flow needs to go and exactly how we want to manipulate the screen
In a declarative approach, we do the opposite, where there is a lot more abstraction and we just tell the computer "I want to create a button" and it creates a button and does not bother us with too much low lying information
[add more...]
To understand the fundamentals of CS, I embarked upon a 4 year long journey of doing a 2nd bachelors degree in Computer Science
Even though I was told that understanding algorithms and data structures would be enough for me to get started, yet what I saw was that the 4 year degree was a testament to the commitment that I was willing to put into the craft of programming and my career as a Full Stack Developer with a specialization in Machine Learning
I now understand and accept that knowing the fundamentals of programming, how computers work at a binary level, how assembly is the bridge between source code written by humans and machine code understood by computers
At its core, its a fascinating subject, one I genuinely wish to master and will, the reason for that being that it will allow me to 100x my capability by overcoming my organic limitations
More to come.
Today I learned how to inspect hard to get elements in the DOM using a CSS trick in the console. So what you basically do is that you go i...
