@lovekencode@masoniteproject no its not dead ive just had serious health issues the past few years. you can start by looking at the issues, finding something that makes sense or ask more questions
https://t.co/aSmKWbOJXI
We just launched Masonite Academy — a dynamic, Codecademy-style site to help you learn Masonite step-by-step. Check it out and support the project so we can keep building! 👉 https://t.co/ZDD3bLTcv9
I'm back on the market for a job and I'd appreciate reposts, thanks! 💪
I'm full-stack Laravel with 10+ years of experience.
I have many strings to my bow, making me valuable to growing startups.
Remote or London area (if you can sponsor a visa).
I’d like to work on educational courses this year for Masonite but I’m stuck on the format.
I want something unique, high quality, interactive. And able to reproduce across topics quickly. Anyone have thoughts?
Hi I have taken a break for the last few months. I was diagnosed with brain cancer in June, had surgery which paralyzed my left side of my body and just been recovering since. Through therapy I was able to regain some control over my left arm and leg.
@zubeio Looking back at zube i can see a module for tickets. This is great for planning but seems very manual. Can it integrate with an email? So people can send emails to like [email protected] and it would create a ticket we can act on? or even reply to?
I received an email that my mortgage loan closing date has been scheduled but not doing a loan closing with this company. Then I get this email:
As an overworked developer myself this pisses me off. clearly an automated email got sent and you want to shame your employees for it?
One of the mistakes that a lot of developers fall into is when they hit an exception in their application, they reopen their editor and look for any mistakes.
Look at the exception message & stack traces. Developers invest time into making these helpful. THEN look at the code