11 karma · joined July 2, 2012
Changing go fmt to enforce the convention is simply making sure that people write code the same and frees the developers from the tireless discussion about which one is better. That alone outweigh any disadvantage of choosing one or the other.
Where are you located? I haven't worked w/ PHP for 8 years and I'm really not sure what the market looks like but learning other newer technologies such as Rails could potentially make a much big market available to you.
I know in the Bay Area, Jr Rails engineers are in super high demand.
That's definitely not a software engineer routine. Engineers craft/architect solutions instead of "wiring shit together". Of course, being able to re-use existing stuff is part of the job but if your job is wiring things together, specially if you do not know how those things work, you're not a software engineer.
That said, there are different software engineering gigs with different level of difficulties and solving different kind of problems. I like the advice of specializing, getting into more computer science, but that's still software engineering.
Don't get fooled just because the market is full of shitty web development gigs, that's a small portion of "software engineering".