I had been a "hobby" programmer for well over a decade, with my primary career being in repair or a "technician". I had taught myself dozens of languages because it was fun, but never really accomplished much.

I was laid off from my job as a technician and I found myself listless and without purpose. I started doing development again on random things to pass the time and I ended up volunteering as a developer for a game I had played for years.

At the same time I had an uncle who encouraged me to consider software as a career. These two things gave me the confidence to apply for a local software job I saw on Indeed.

They called me pretty quickly, and I was brutally honest. "No, I don't have a degree. I'm self-taught. I have no professional experience really."

I got a proficiency exam anyway and I took it - apparently doing well enough on it that the CTO called me a week later. We had a long talk and I finally asked him why he called me.

He told me that while a degree means something, the passion to learn this job means more to him. It was a month before I was offered the position, and I graciously accepted it.

We had a call about my compensation before starting. It was rather low, but we both agreed that my skill level was quite an unknown.

A year later and my pay was bumped up a sizable amount. My skills are defined now and growing rapidly as new challenges are sent my way. I went from a naive hobbyist to a professional in a short period of time.

I realized that I was always a professional. I had a desire to learn and a desire to do things the right way. I may not have known what to call things. I didn't know some of the design patterns I had used over the years were standards that had names and meaning.

I basically work two jobs now. My full-time job and also on the game that helped propel my career forward and gave me the confidence to reach for it.

As for my hobby? I turned to electronics and the maker community. It's a nice marriage with my programming skill set, and I never knew how rewarding a blinking LED would be. :)

Stop fooling yourself by thinking that the hurry & pressure will eventually go away if you work overtime & stretch yourself to heroics weekly. They won't, and they never will (and even shouldn't). Focus on building sustainable habits that propel you towards your goals day by day, and don't give up until you're where you want to be. Period.

People tell me all thw time that I should use Laravel...
Sure... when Laravel supports Propel out of the box...

TL;DR: "Best" job is a dynamic flow, your job or your priorities will change, better to just start.

It depends on your definition of "best": do you mean the job that you think you will enjoy the most? The job that you are the most knowledgeable on? The job that you will have the most upward mobility in terms of opportunity for promotions and salary increases?

All of them at once, i suppose, but you cant have everything at once: my advice would be just start somewhere. Thinking you're going to get your dream job fresh out of college is a bad way to look at the world. The best job may be the best right now, but your priorities will change in life.

The best job today may not be the best tomorrow for a variety of reasons, but if you start somewhere, you will always have the experience generated by your existing occupation to carry you forward and propel you into your next big position.

# ./symfony test:unit

Propel-Exception: Unable to execute DELTE ALL statement [...] Integrity constraint violation: 1451 Cannot delete or update a parent row: a foreign key constraint fails.

WHY ist a UNIT TEST reaching out to a REAL data base?
And who in their right mind would create a different data base schema for the tests?
This was with a clone of the real thing. Removing the FK results in double PK-errors...

I would have wanted to bring up SICP again, with the great big warning about the evil assignment operator and state and all the troubles that ensue (just think: concurrency).
But in a way, nothing has really come up from this or my attempts to dig deeper into "everything is a file/object" (Unix, smalltalk), neither from formal languages or the Curry-Howard correspondence. - Maybe there's just nothing, no firm bottom ground to discover. Like the physicists going for their world formula, but instead of a grand, beautiful symmetry that explains everything, we face a shattered world of (incompatible) theories, that is ever so more complex and chaotic through our theories applied to it. There may not be a Platonic ideal world of ideas, but rather partial constructs explaining some particular perceptions.

Similarly the one perfect programming language to rule them all, the perfect abstraction, pattern is probably just another prepubertal fantasy to be sunk.

So maybe instead of seeking the perfect epiphany, we should go for something quite different: the nagging, brooding uneasiness that something is wrong there, that there's something to be fixed... that even negative feeling would propel us to search further, not to stay in whatever is touted as the real thing.

Such irritations I found with Pieter Hintjens' writings. For example when he actively engaged in conspiracy theories. And I'm still not sure, if he just went off the cliff or he's even right alluding that these theories are an act of sanity, a self-defence against the hidden evil mights. I just don't know. Anything.