> In the end, you have much less control than you think you do.
I love how you articulated this.
It really sums up how I feel them times I get too strict on things "because it will be good for their future". Not saying it is not necessary sometimes, but don't expect things will work as planned regardless how much you enforce it.
Not really, you were able to run everything inside a virtual host under a specific user+group. That was key for cPanel which is what you would usually get when purchasing a shared hosting account in the 2000s until "the cloud" became a thing. https://cpanel.net
We are building the next-gen pet platform. If you love puppies and technology, you will love working with us!
Experienced Laravel developer that have experience working on a product from start to end, from including technical decisions, deploy, and maintenance.
Required ability to work in UTC-3 or UTC-5 timezones.
I personally worked with both and have VueDevTools and ReactDevTools extensions installed, and I am impressed by the number of websites React icon turns on compared to Vue. Which would mean is has a huge chance of becoming a standard for the next few years.
Started as a freelancer, got too many projects at the same time. Could not meet any deadline and got burned out. Everybody lose.
Build up a small dev team, got too many projects again and got a single person working on three projects at a time. Same thing: long days, too little progress, could not meet deadlines. Everybody lose.
The issue with dev work and switching between projects is that is takes a few minutes to an hour to focus and get really productive.
With experience you will find what is the equation that works for you. In my case I do not do more than one dev/code work at a given time or quality starts to degrade.
I can provide consulting, answer questions and do estimes on other projects while coding, but only one dev work at a time.