You can definitely clear the first round of an interview for a programmer or a software engineering job. However, you will find it very difficult to clear the technical round where they will ask you all sorts of questions. In this article, we focus on the top 10 tips for facing any type of technical screening process.
The skills of data experts are becoming outdated as the industry evolves. If you’re looking to learn data science – quickly – then you’re in luck. Bootcamps of all kinds have sprouted up to help the surge towards data science move faster. Here are six best places to learn data science in half the average time.
There are many types of programmers you may encounter in a team, starting with those who think they know it all and ending with the lone wolves who hate the idea of working with others. Some may spend too much time thinking about unnecessary details and all the backup plans the project does not need while others may ignore every guidance, process or discipline possible. But does this mean they don’t have anything in common?
In the future, everyone will be a programmer for 15 minutes. How is that possible? We talked to Felienne Hermans, assistant professor at Delft University of Technology and Software Architecture Summit speaker, about the difference between a professional developer and what she calls „end-user programmer.“
Pair programming can be a nightmare for some developers; for others, it’s normality. In a previous article, we revealed the perks and pitfalls of pair programming. Now we are trying to answer the following question: Full time or part time pair programming —which one is better?
Some view the transition from engineer to manager as pure torture, others simply want to move up but just a few are truly aware of the benefits and risks of juggling passion for code and management responsibilities. How do you know if you are cut out to be an engineering manager?
There’s a famous saying by Roman philosopher Seneca which goes like this: “It is quality rather than quantity that matters.” This quote transcends time and industry and proves that countries such as the United States and India, famous for their huge number of programmers, are lagging behind in terms of quality. Curious to see which countries would take home the gold, silver and bronze medals?
We opened Pandora’s box because we wanted to know how developers really feel about interruptions. It turns out that interruptions (especially planned ones) truly are real-life kryptonite and they can hinder productivity. Developers weighed in on this issue on Reddit — so let’s see how they cope with interruptions.
It’s that time of the year again! According to Puppet’s newest DevOps Salary Report, “DevOps engineers, architects, software developers and engineers, and systems developers and engineers in the United States are more likely than not to make more than $100,000.” Let’s see what else is new.
People need roughly 23 minutes to go back to their tasks after a major interruption, but the plot deepens if you’re a programmer. Add at least 10 minutes to the forced break (the minimum amount of time you need to start editing code again) and there you go — that’s a solid half hour you lose whenever someone approaches you. It gets worse if that interruption is planned.
The million-dollar question about the level of productivity in software development teams is the following: How does their productivity scale with the team size? Forget everything you knew about the ideal team size. Are you familiar with the Ringelmann effect?
Finding a remote job may sometimes feel like you are looking for a needle in a haystack. Many websites have accepted the challenge of giving programmers an overview of what the market looks like and what companies are willing to hire talent without forcing them to move anywhere in the proximity of the mother ship, but that doesn’t mean they all deliver that promise. Let’s see which are the best places to find a programming job.
In this article Henrik Warne, a Stockholm-based software developer, weighs in on the details that transform a good programmer into a great one.
Creating software is an emotional process for the team members who all want to see it succeed, and this can create tension. The phrase “you have to pick and choose your battles” is commonly used. But how do you make those decisions?