itrollpussies

I still can't read the full story.

Nice job , looks really cool.

PHP is really cool, the reason I created an account here is cos someone was bashing PHP, so I had to troll him.

There is a but though, don't make PHP your last language, broaden your horizon.

It's more of like doing system designing (pre-planning), the system design stage is way of looking at the bigger picture by connecting the dots, and yh, it could be a mind thing but I mostly use my pen and paper or if it's something that's really difficult to nail, I use the C4 modeling (you can use whiteboard, paper or any C4 modeling tool).

C4 modeling would give you the abstract design or system architecture graph, you don't have to do all 4 levels diagram, just do the one that makes sense to you.

If you are doing something simple, you might not need to do any of that but as soon as you are building something of scale with optimal security not doing system designing is like building a skyscraper with no design, well, you know what might go wrong :)

I am not trolling today, TDD doesn't make any sense to me, testing to fail and correcting it until it passes doesn't work with my flow.

In a DAW(Digital Audio Workstation), this is like adjusting the knobs, adding effects when you haven't even added any samples, it just doesn't make any sense, stop forcing yourself to do things that doesn't align with your flow, you'll likely get annoyed for no reason.

The way I work is I do the architecture design, I write the code, then I write my test by following the design graph.

If I don't know what the design would look like, I do what I call "code freestyling" to get a basic idea of what the overall design would look like then I repeat the above step.

I see OSI version of open source as forced labor, the best I can do is open source my work, meaning make the source code open source, people can use it for free but as soon as you want to commercialize my work, you gotta pay.

If you anyone is about to say that isn't open source, well, there is nothing you can do about it, sorry

I use a couple, some I discovered along the way, some I leanrt:

Event and Event Handlers: I rely heavily on this one, event handlers subscribes to an event or you queue them to a certain event, when that event is emitted, it relays the info to the handlers which do their own thing. This pattern is simple, flexible but can be problematic sometimes (i.e. annoying if there is no async support, tight coupling if you are not careful, etc).

Hookers: This is inspired by the event pattern above, I use this in my Template System. The way it works is I build a base template, then I define the segment (hooks) I want to extend if I am to reuse the base template. Just like event handlers, you also subscribe to hooks but in this case, it is done directly in templates reusing the base.

I took this one step further, you can have hooks within hooks, remove a particular hook with their respective handlers, hook before a hook and hook after a hook. Very flexible and speeds up building page templates.

State Pattern: I use this one for breaking down complex problems, it works but you can easily shoot yourself in the foot.

Pattern makes sense if you understand the "Problem Space", if you do understand the problem you are solving, the pattern to use would come naturally (sometimes you do need to freestyle around to see which would one would make sense)

I can't find it either, which is why I said they should have linked it. In Microsoft Store, you'll see Free+, meaning the base version of this app is free, but there are in-app purchases.

Looks okay but they should have added like a pricing page since it's not free.

Sometimes, it amazes me how some of you reason, the article deeply reflected on some crucial things that I personally I can relate to, and the only thing you could point out is one stupid famous quote that know one has idea about.

Give foolishness a break, at least for a week.