The Problem With So-Called Microframeworks

As someone who has been doing web projects for quite a while, I can safely say that I’ve seen a large number of solutions pop up over the years, which in the end pretty much do the same. In recent years, I’ve been noticing the rise of microframeworks. While I understand the inherent desire for a lighter code base, what I’ve found as a primary weakness is that there’s a lack of features that most people probably want out of the box.

Continue reading “The Problem With So-Called Microframeworks”

Python Flask: Message Flashing Session Issue

I have to say it: the Flask documents are pretty bad. The code is chunked up, abbreviated, poorly explained and no comments to really go through every little detail, which often leads to bizarre errors for the inexperienced programmer. Even for an experienced programmer, there’s some things that just are really mysterious or need far more depth. But I want to show something simple.

Continue reading “Python Flask: Message Flashing Session Issue”

Developers are Fucking Retards

At the risk of alienating myself from the development community at large, I want to rant a bit about why I believe developers are fucking retards. As someone in the tech industry for 16+ years and someone who’s been coding for even longer, I’ve seen things go in circles that I had hoped would lead to something profound. Instead, I’ve come to realize that instead of moving forward constantly a lot of the industry goes through it’s Dark Age periods and with the web and mobile, it’s probably at it’s lowest point.

Continue reading “Developers are Fucking Retards”

Laravel: The Ugly Command/Event – Handler System

One distinctive feature Laravel has as part of its optional architecture is the command/event system. Commands are supposed to represent single, discrete pieces of logic that ought to handle a particular job. Events are ways to notify the system that something occurred. Both commands and event employ handlers and commands can implement the SelfHandling interface to combine containing the data of a Command object along with executing the command itself. While the ideas are great, the implementation still is messy and I want to talk about some flaws in the architecture that bluntly stated don’t make a lot of sense to me.

Continue reading “Laravel: The Ugly Command/Event – Handler System”

Homestead: Dealing With Vagrant’s Permission Issues

The other day I ran into a really annoying issue where after re-doing my Vagrant instance, I had some issues with the way my directory was mounted and provided certain permissions. When I would ssh into my box and tried to change permissions, even as root, the permission layout would stay the same. However, I needed to deal with saving files to a certain directory, which was driving me nuts. Here’s how I did a quick solve.

Continue reading “Homestead: Dealing With Vagrant’s Permission Issues”

Laravel 5: .env APP_ENV not Being Read Properly and Quick Fix

So I encountered an issue with Laravel 5 where your APP_ENV in the .env file might not be read. Even if you change it through the Homstead.yaml file, change /etc/php5/fpm/php-fpm.conf, change your .profile file, etc. you still may not see the variable properly reflected when doing something like var_dump($_SERVER) or examining the Application::Environment() function. This post discusses what the issue is and a quick fix for this problem.

Continue reading “Laravel 5: .env APP_ENV not Being Read Properly and Quick Fix”

Laravel: Adding A Default Message to a Select Drop Down with Eloquent

I ran into an issue earlier where I needed to add a default message to a drop down box created through Laravel’s Form builder. The difficulty was that the form select doesn’t allow for a default option. You have to manually add that. If you pre-populate your select with an Eloquent model, you will have to deal with using a Collection. So how can you add to put an item at the head of the list?

Continue reading “Laravel: Adding A Default Message to a Select Drop Down with Eloquent”