People-professionals are working in IT, not robots
In fact the average competition for one workplace in IT is about 500 people – the market lacks specialists! You can find and read more. It's not hard to find on the internet
Need specialists who know their business!
For this reason, I wrote about how to become one and what you should pay attention to at the beginning of your journey. Even have my presentation with IT-directions! Also I understand something in Game Development..
Flew!🐌
I just started to learn Game Development, and decided to run write my personal blog about it. So there you can find information(resources, blogs, courses, books) that i've gathered and my personal problems with learning)
Hello! My name is Mikhail Emelyanov, I am embedded software engineer, and I was inspired to write this little roadmap on the capabilities of Python language by a certain commonality among the existing Python tutorials found on the web.
The usual suggestions to study, say, “Algorithms and Data Structures” or “Databases” are especially jarring. You can spend years studying these topics, and even after decades you'd still be able to find something you didn't know yet even without ever venturing outside the scope of Algorithms!
Using video game analogies, we can say that novice programmers often stand on the shore of the lake of boiling lava with an island with the ever-coveted jobs in the center, while the islands in between, which you have to jump on, gradually increasing your skills in successive mini-quests, are either missing, or arranged haphazardly, or their fairly smooth sequence breaks off, never having managed to get you any farther from the shore. Let's try to build a path of hint islands, a number of which, although not without effort, will finally allow us to reach our goal.
A job interview is one of the most stressful life events. According to research IT specialists change their jobs every 2-3 years, and every tame they are faced with interviews with HR, tech leads and future managers. Artem Golovachev, Director of IT architecture at Innotech, shares his insights on how to successfully pass an interview.
Testers and developers are the driving force of any IT enterprise. Their work directly influences the quality of the final product. Pavel Petrov, our Lead tester-engineer of the risk detection monitoring service for corporate clients, shares his insights on building a productive relationship between two different IT camps.
I wonder why IT developer interviews are so strange most of the time. It feels as if the people are looking for computer science teachers, not engineers. All those theoretical questions that have no relation to the working reality. It is strange to be looking for eloquent teachers, who can perfectly explain any term or pattern, and then ask them to do the actual work. Maybe it is the imprint from the years spent in university when the teachers looked like all-knowing gods and seemed to solve any issue in your life. May be, may not. Anyway, these teachers stay in unis and don't do the work.
You know, what would be my universal answer to all interview questions? “I have no idea how and why it works, but I can use it, and I can use it for good”. This is the reality. Actually, no one knows exactly these hows and whys. What is a computer? What is electricity? What is an electron? No one knows for sure. But it works and we use it.
Imagine a famous author, like Stephen King, asked a question about the difference between deus ex machina and Mary Sue. Would his answer change the quality of his books? He may or he may not know all those scientific literature terms, but he can use the language and use it for good.
Every time I turn on my computer it is a wonder. I have no idea what is going on, but it awakes, it becomes alive, and I can communicate with it in its own sublime and subtle language.
Have you ever realised that all these electronic devices are monsters, Frankenstein's monsters? Some pieces of dead matter were put together, and then, with some electricity involved, it suddenly awoke. “It's alive!”. Had Frankenstein any idea why it turned alive? Of course not, or why he was so surprised? Every developer experiences this feeling almost every day. “It's working!”
This is a set of chapters for young engineers. We give practical advice and discuss goals, challenges and approaches used in modern software engineering.
Along with classical foundations this article contains original ideas of conceptualizing engineer's work with emphasis on bringing order to the situation and finding an insight. Engineering is approached as work in uncertainty with other people which requires special skills. Non-obvious complications regarding modern production in big companies are discussed.
This article is based on 15 years of experience in engineering and management in high-tech industries.
Nothing and nobody will escape oblivion. Whatever you may say, the history of mankind is a history of automation and the subsequent evolution of workers. This happened both during the first industrial revolution and during the second. The same thing happened with digital revolution. Now machine learning and artificial intelligence are being implemented everywhere. What is the future of software testing?
There is a myriad of articles about where to find remote jobs, particularly in tech. Some of them are outdated and most of them don't provide detailed reviews. So that's why I decided to do my own research. I did a basic search by "React" skill (where possible) and expected to see mostly "Frontend Developer" vacancies.
It may seem that when you are a beginner, you'll do simple things only. No need to learn data structures and algorithms. No need to understand Big O notation, complexity and stuff like that.
This couldn't be further away from the truth!
In 2008, when I just started learning to program, I spent a lot of time reading books on PHP and MySQL. Months later, when I felt confident, I took my first freelance project. It was a real estate website. A simple one. I used a custom-made ORM and everything worked just fine!
When I released it, the search feature quickly became sluggish and made the website unusable.
I was wondering what the heck had happened. I figured out that database queries became very slow when there were over 200 real estate objects added to it.
This is it. What worked fine during testing did not work in real life.
I was a self-taught developer. I did not know how to measure if my project scaled well. I didn't even know that I had to do it.
I thought algorithms mattered only for launching a spaceship.
If I had some basic understanding of algorithms, I would have known that the more the input, the longer it takes.
I am not saying I would have come up with a robust solution as a junior, but I would have looked for a solution because I knew there would be a problem.
Please, don't make the same mistake!
Of course, data structures and algorithms are much more than that and they apply differently depending on what you work on.
But a basic understanding of data structures and algorithms is a must for every software developer.
Hey Habr! I'm Ruslan, a Java programmer with experience in IT of 15 years who still doesn't understand how to grow as a technical specialist in a company.
“In 1665, Cambridge University closed because of the plague. Issac Newton decided to work from home. He discovered calculus & the laws of motion.”
