Doctrine is one of the most used ORMs in PHPLand, with many applications heavily coupled to it. With more and more companies moving to microservices one of the tasks is to migrate their entities to come from the microservice instead of from Doctrine. Here I’ll describe how I migrated an entity so that it was stored in a Microservice instead of MySQL and came from Doctrine. In my approach I used the original entity class, this allowed for using feature flags for migrating each repository method one at a time.
Estimations are one of the most important parts of project planning and one of the most common tasks that developers do no matter which language they code in, what team they are on, or which company they work for. Estimating is hard, so hard we pretty much get it wrong a lot of the time. Not enough details - guesstimates Estimating without enough information is in my opinion of the leading causes of estimating poorly and causes project overruns.
Code review is the process of having others review code that is written and accepting feedback and adapting the code to the feedback given. These days code review is seemingly at every IT department and widely ruled agreed upon as a best practice. It is often one of the largest sources of conflicts within a development team since giving and receiving criticism about work is often hard to do while remaining detached from the work itself.
This is just a rant post to get it off my mind. No names will be mentioned. So I recently discovered a tech company was relying solely on volunteers to develop part of their product and were unable to provide support The volunteers didn’t realise that tech support for the code was basically customer support. Everyone’s response was “this is OSS” as that excused a company having zero employees supporting a part of their product.
Several months ago, I decided that I wanted to generate some income from my own projects. I originally started on a SaaS bootstrap library. A part of my development work for that library would need to be demos to prove the project and that I would try and sell each demo. Since doing that, I learned nothing about starting a business, so I began to read books on the subject. I read over 10 books during December alone.
So last night I managed to get myself into a twitter fight that I think brings up an important aspect of software development and highlights two different mindsets within the software development world. So here I will try to explain my position and theirs in a better format than 280 characters and while it’s not 3am. Quick Breakdown of the Fight The Twitter fight was over the idea that there are some bugs found by QA in code that has been in production for years and has never happened to another person ever and these bugs aren’t worth fixing.
So it’s yet another ProductHunt release blog post. This time it’s not to get that sweet, sweet traffic to my project but just to actually reflect about it. There were some things I really didn’t expect to happen, and I read a bunch of these blog posts for some reason. So here is my breakdown of “launching” my CRM side project Easio. One major thing to do So I realised there is one major thing that everyone who is going to use product hunt to launch their next big thing.
Here I try to explain in nontechnical ways things that happen in IT departments which in my opinion are generally harmful to the company. The aim of this series is to help company founders who aren’t experienced in IT be able to judge the health of their IT department. The Product Team is there to decide which features are to built first and how the features are to work. They are one of the most crucial parts of the development processes since they choose the path for the project and help make sure that the project brings the most business value as possible.
Over the years of leading teams and working in various IT environments I’ve discovered, there are generally three types of tickets within the small to medium size companies. An Idea An Idea Request is where someone has an idea, and it would be nice to try it out and see if it works or not. An idea is not a request that is based on current business needs but on the possibility to improve something that is already working.
For the most part, sanity checks are put into the code to ensure there are no bugs. For this reason, guaranteeing sanity checks are done correctly becomes necessary. If you do not check to see if the data is valid, and it is invalid, then you’re going to allow invalid data to proceed. Here, I’m going to discuss how I think we should do sanity checking in PHP. Asserting Valid Data What I’ve seen a lot is people are asserting for invalid data when they’re doing their sanity check.