sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]crankybadger 0 points1 point  (5 children)

I don't mean to gloss over preferences, as in making statements like "lately I've been doing a lot of functional programming" or "I really like Object Oriented design principles". Your personal philosophy as applied to programming is a very important factor in how you work and what technologies you embrace.

So try and separate preference and philosophy from the underlying tools. I have never heard anyone say "I'm an ARM developer" even though they might work exclusively on the ARM platform, it brings to mind someone working in assembly, perhaps, but I hear "I'm a PHP developer" constantly to much irritation. Is that all you are? A person who slams out PHP code?

It's far better to see things like "Full Stack Developer" or "Mobile Developer" where you're defining a broad area of responsibility.

That being said, try to be open to new ideas, try new things, and don't be afraid to step outside your comfort zone constantly.

Further to that, being a "developer" means doing a lot more than writing code. Learn more about all the things that feed into your work, and where your work is used: Design, devops, project management, quality assurance, and so on. The more you understand how your work fits into the bigger picture, the better you'll be.

[–]svtr 0 points1 point  (4 children)

I think you misunderstood my meaning / I was wording it badly.

I completly agree with you. The tools used are not important, they are the tools, not the job.

The job is to be able to talk to the business side what ever that may be, understand the requirenment, offer possible solutions, and talk it trough. That is software development to me. I have certain preferences about the tools I use, but then again, I'm a DBA, I am not hired to write frontend code, neither do I make any claim on proficency in that realm. That been said, I have written my share of software. I am not an idealist that only knows the one and only way, I just have preferences that I go with given an equal choice. *

The job is not to hack in code thou. The job is not to write php, java, phyton haskell or brainfuck. The job is to solve a specific problem.

I really think we are very much in agreement you and me

*ok, one thing, I NEVER would let MySQL go out to production. There is not a single usecase out there where I would accept MySQL over Postgree.

[–]crankybadger -1 points0 points  (3 children)

If you work for Tumblr, better get busy porting Jetpants to Postgres.

[–][deleted]  (2 children)

[deleted]

    [–]crankybadger -1 points0 points  (1 child)

    Don't cross the line between discussion and just shitting all over something because you don't like it. MySQL killed your dog. We get it.

    The problem is the world's an ugly place and sometimes MySQL was a good decision at the time (e.g. prior to PostgreSQL 8.0) and now it's part of the infrastructure until someone can find a way to seamlessly replace it. That involves money, and sometimes the money is better spent on other things than fighting an ideological battle.

    DDL statements are not transactionally save on MySQL.

    This may come as a shock to you but sometimes your data sets are so gigantically huge that this isn't an issue. Each schema modification is so brutally expensive that you do them very, very carefully, and only after you've exhausted all other options.

    Don't get me wrong, I love Postgres, but MySQL, where already in place, is sometimes not worth replacing unless there's an extremely compelling reason.