Start from understanding the needs and point of view of the organization. Take care of good communication with customers. Don’t be afraid to develop both technical and soft skills. You will have a lot of battles at work. Choose wisely what you can engage in, given your limited time capacity. Act locally, think globally to change the project in small steps. Use non-hanging fruit to be successful and avoid burnout.
In my opinion, the best investment is our development. It allows us to achieve better results, receives promotions, and increase our remuneration. By investing in ourselves, we invest in our future. You didn’t know everything (and you still don’t know everything). It is worth trying to help others and learning at the same time.
Many applications introduce some kind of status to make it easier to share data. However, more and more modules in your codebase need to be explicit about these assumptions. Views can eliminate the problematic SQL query. It’s also great way to introduce well-defined entities.
Understanding exactly what SQL commands are running is helpful to ensure safe migrations. By default, Ecto does not log the raw SQL. However, we can change it.
Understanding the business is critical. It allows you to achieve better results in a shorter time. Don’t try to be an expert right away. Learn and don’t be afraid to ask when something is unclear. A common language is an opportunity for discussion with the client.
Let’s check what has changed in the latest version of Elixir. Most interesting, from my perspective, will be improving compilation time. However, that’s not all! New map support, information logging level and changes inside Inspect are waiting for you.
What if a dependency is no longer needed? One library less is potentially one place of conflict between different versions of dependencies less. You can do it with one command, and clear your lock file.
You may be surprised, but the behavior of the popular
inspect can be easily modified. Maybe it will make your daily work easier and make it a bit more comfortable.
Automated testing can unburden Quality Assurance teams from the monotonous manual review of every change. They can also be a great acceleration for programmers. But they won’t make your organization or product great overnight. It would help if you had people’s support, a clear plan, and an understanding of expectations.
The more time we have to do the job (especially in the office), the longer it takes. Work complicates to fill the available time. Check out Parkinson’s Law and understand why!
Everything around us makes us concentrate on what is available immediately and instantly. Short-term gains and results are much more appreciated than long-term with much better results. Long-term thinking and acting following this thought is the key to a peaceful life on your own terms.
A simple example of how to introduce a Universally unique identifier (UUID) into your project. You just need to remember a small modification in the migration and the column type change.
Have you wondered about the nature of technology? Technology is neither good nor bad, nor is it neutral. The invention is the mother of necessity. The same technology may have completely different results. New needs, as well as new technical possibilities, make the impossible possible.
Positional bindings can be problematic due to the order when building large queries with many different functions. Named bindings can be of great help in our challenges. It is not necessary to know the position to be able to refer to the variable. Creating reusable and maintainable queries doesn’t have to be complicated.
Don’t be afraid to make mistakes. Even the best programmers make mistakes. However, minimize their impact and react quickly to the most critical problems. It is much better to make mistakes but fix them quickly than to delay the development phase and not provide functionality.