Usually we like to think about what the primary use case is and then what fits that as a maintainable solution. Normally if its a high content, but low functionality requirement i'd consider a cms like wp. If its more functionality heavy then you want a stronger and more expandable framework like Laravel. Decide what would work best for your criteria, and if that criteria is learning, theres never anything wrong with taking the road less traveled... but only on training stuff, cant stand it when someone builds a paid for project in something they know nothing about and then just uses that as an excuse. Become proficient, then produce.

Asnyc attitude... single threaded attention span?

Absolutely, when you have a PM who has no ability to comprehend anything relating to management in the slightest, your own work somehow seems to become a secondary objective.

// this section should never run, if it was, call an exorcist... im out

@taylan we most certainly are! I identify as a code orangutan!

// @TODO: laugh

Depends on how deep you want to go. Laravel projects ibe built are all fantastic when simple and direct aproaches are the name of the game. Codeigniter projects have always only been a case of "we need as much control as possible and we want to purpose bulid the lower level logic in the framework".

2c thought

@Lisanna i think its a habbit born more from a case of saved changes taking effect whilst testing than recovering after a fault.

@OnyxDarkKnight better save my saved work.

@kanduvisla thats the best part. Its fantastic to be able to see a case from a before & after 4yr perspective of an individuals developments.
However amusing it may be at times :)

2c Comment.

This kind of thing shorthand in php is usefull for.

$cat = ( $cat=='venue' ? 1 : 0 );

@scrptd random thought poped into my mind after reading your comment. Integrate in some way/shape/form with the likes of stack exchange. Now wouldnt that be something. Only particularly relevant to the rants about code as oposed to dev life. Yet interesting none the less.

@lreading this... exactly this!

Oddly enough i have noticed i have a preference as follows:

conditional/itterator
{
}

function/decleration {
}

And frankly i havent a clue as to why

@dfox perhaps if out of app comms were to be taken up for whatever reason, perhaps a feature to extend a business card like.. thing.
Use case: I want to help this person with this specific problem they have ranted about
> give them details via which to contact me. (In app or otherwise)

(2c thought)

Dev fucks up > adds 4hrs+ to their day.
PM fucks up > adds 4hrs+ to devs day.
Lifecycle of development

Accurate to the tee: https://m.youtube.com/watch/...

Bug report comes in > feature approval goes out!

I dont have issue with people commiting broken/in progress code, Assuming its branched for an in progress feature. But if i pull a master branch and its not functional, i will reset that head... --hard