What's your development environment like?

images

watched that movie last night

you could really see denzel enjoyed the fuck out of playing that role. good shit
 


my development environment is a dungeon full of ninjas torturing virgins. i work to the soothing sound of their piercing screams. it keeps my soul from fracturing into ten thousand tiny parts when exposed to the greatness of my code.
 
my development environment is a dungeon full of ninjas torturing virgins. i work to the soothing sound of their piercing screams. it keeps my soul from fracturing into ten thousand tiny parts when exposed to the greatness of my code.

I thought I was the only one that used this.

However, in my defense, I don't do ninjas torturing virgins, but rather barbarians. They've got a little more oomph behind 'em.
 
When developing sites locally, I use EasyPHP, which consists of Apache, PHP, MySQL and PhpMyAdmin. It's portable and installed in my Dropbox directory.

This allows me to work from anywhere (where my Dropbox is installed) and it gives me automated backups.

For editing, it's UltraEdit on one computer and Notepad++ on another. I prefer UltraEdit, but I will check the editors mentioned in this thread.
 
That fact that you would shun code completion or a good IDE, but prop frameworks for their speed of development is an oxymoron.

Code completion allows you to code faster and more accurately, which is the same argument for being pro-frameworks. The fact I can auto complete something like variable name or a function name means I make less mistakes during the process. It also keeps you from making functions to long function names. Personal pet peeve of mine. A good example of this is when people in PHP make a function like toDB() that runs mysql_real_escape_string(). It makes no sense that you would write a function to a function, I just want to facepalm.

The IDE will also bitch at you if you type something that doesn't make sense and allow you to catch some run time errors before you execute the code. I'm pretty damn good at bug hunting but it's not where you want to spend your time. I know what retarded features right?

I'm going to show you that you don't know what you're talking about by completely flipping every single point you made and making you realize that your argument makes no sense. READY!?!?

dchuk said:
That fact that you would knock on frameworks, but prop code completion for its speed of development is an oxymoron.

Frameworks allow you to code faster and more accurately, which is the same argument for being pro-code completion. The fact I can reference something like a framework's variable name or a function name means I make less mistakes during the process. It also keeps you from making functions to long function names. Personal pet peeve of mine. A good example of this is when people in PHP make a function like toDB() that runs mysql_real_escape_string(). It makes no sense that you would write a function to a function, I just want to facepalm.

The framework will also bitch at you if you type something that doesn't make sense and allow you to catch some run time errors upon execution by providing a full stack trace of the error. I'm pretty damn good at bug hunting but it's not where you want to spend your time. I know what retarded features right?

enhanced-buzz-15854-1300424464-1.jpg
 
I use GitHub, NetBeans 7.1, Remote Server Project, FileZilla, PivotalTracker

Instead of Remote Server Project use Local Server with something like XAMPP
 
Anyone who tells you to not use a framework or that frameworks are a waste is, get ready for it, AN IGNORANT CODER. Ignorant coders cost you money. They spend time working on solved problems. Their list of inventions consists entirely of wheels. One of the best realizations a professional coder can come to in his career is the one where you finally understand that there are a shit ton of coders out there who are infinitely smarter than me, and I should be using, hacking at, and learning from their code rather than attacking every problem with my ten fingers and that thing between my ears.

Schooled.

Rage, you seem to think frameworks are mostly used by people who are beginner programmers but I'd argue it's the other way around. People progress from coding everything themself to understand it, then move onto frameworks to save time and effort.

And what kind of framework do you think we're talking about, not all were created equal. I use Zend Framework for PHP which can be used just as a libary if you don't want to use the MVC.

As an example, if you're working with the Amazon API and are not using Zend_Service_Amazon you are 100% re-inventing the wheel and wasting loads of time.

I was the same as you and avoided frameworks as long as possible but as you admit yourself, you're in the minority and not everyone can be a retarded programming hipster jumping to the shiny new thing.

At least tell me you've accepted that regex is quicker *to write* than multiple explode functions when writing a scraper?!
http://www.wickedfire.com/automation/114261-botting-q-thread-ask-away.html#post1146993
 
I think frameworks are fine for handling complex things that would be stupid to code from scratch, such as an amazon api, where it'd take you longer to learn the ins and outs and code it for yourself than to learn the framework's implementation of it, but to use frameworks for everything, like sql queries or forms or basic PHP functionality... that's nearly as stupid imo. It's like, I need to do a simple sql query so I'm going to initiate a new instance of this huge bloated class, then form my query as an array and all this other crap... Completely unnecessary.

Also, just because someone doesn't use a framework doesn't mean they're not encapsulating commonly-used routines into functions.

And, if you want to do something that is complex and a waste to code from scratch, you can often find a class or function to do it without incorporating a framework. Sure you should be careful of using code that you turned up with a google search, but for many things there are popular, tested classes to handle just your specific need. And then you can more easily edit it and strip away what you don't need.

To me, using a framework is a bit like carrying around one of these
thisisaknife.jpg
 
I think frameworks are fine for handling complex things that would be stupid to code from scratch, such as an amazon api, where it'd take you longer to learn the ins and outs and code it for yourself than to learn the framework's implementation of it, but to use frameworks for everything, like sql queries or forms or basic PHP functionality... that's nearly as stupid imo. It's like, I need to do a simple sql query so I'm going to initiate a new instance of this huge bloated class, then form my query as an array and all this other crap... Completely unnecessary.

Also, just because someone doesn't use a framework doesn't mean they're not encapsulating commonly-used routines into functions.

And, if you want to do something that is complex and a waste to code from scratch, you can often find a class or function to do it without incorporating a framework. Sure you should be careful of using code that you turned up with a google search, but for many things there are popular, tested classes to handle just your specific need. And then you can more easily edit it and strip away what you don't need.

To me, using a framework is a bit like carrying around one of these
thisisaknife.jpg

EDIT: Fuck it, I don't even care anymore. If you think it's a good idea to not use high quality pre-existing code via frameworks to create clean, manageable, maintainable apps, I simply never want to 1) work with you 2) have you work for me.

Coders who are anti-frameworks are anti-intelligence and I'm anti-you.
 
I use dropbox, notepad++ and filezilla. Notepad++ and filezilla are avaliable as portable apps so i can carry my whole coding setup in my pocket.

Im new to version control but it seems like a good idea and not using git and dropbox together so maybe i'm look in to it.

Found this on the subject:

On Version Control

Still not sure i understand it tho :/

Also, dreamweaver sucks ass.

:D
 
dchuk and rage9 both make good points. A newbie should learn without frameworks, but to say that Frameworks are useless is pretty dumb. If you're working with PHP, you'll notice that some of the best developers are working on Zend Framework, CakePHP, Symfony and various other Frameworks. Many Enterprise applications are running on Frameworks.

If you think it's cool not to use frameworks, then why even use PHP? Why not C? Why not create your own language? Frameworks are like having a team of developers developing solid code that is there at your disposal, any time you need it. They're thoroughly testing and developing the framework daily, and most utilize Enterprise Patterns to allow decoupling for ease of use in other frameworks.

Also, if you truly believe that Frameworks don't save time... well... I'm not sure if you've ever used a solid framework in your life. I work with Zend Framework and it saves hours just getting things setup. I know the same can be said about Rails, Django, etc. There's a reason they're popular, and there's a reason most startup's use them.

If you like hacking, that's cool. But people who use Frameworks like to get things done, have more security (assuming they use the frameworks correctly) and have more time to focus on writing tests, which, ironically, most frameworks make easier, too.
 
If you think it's cool not to use frameworks, then why even use PHP? Why not C? Why not create your own language?

Ah c'mon you pro-framework guys are stretching things just a liiiitle bit lol

If the things that are in frameworks were necessary, they'd be in the core PHP code. But they're not, so they're not.
Yes lots of smart people use frameworks, but lots of smart people also created and maintain the core PHP code, and they haven't thrown all that junk in there. So it's really not an issue of "frameworks vs stupidity", it's a matter of preference.

Personally if there's something that I'm going to be using over and over, maybe in more than one project, I'd rather take the time and code that myself, depending of course on the complexity and time needed, and the payoff in terms of learning how it works, being able to customize it, strip it down, alter it however I want. It's kinda like using a WYSIWYG editor versus doing HTML coding in a text editor. I want the code to be a certain way; I don't care if a WYSIWYG can get it done faster and easier or not.
 
My point is that Frameworks provide you with tools that exist inside that framework. Tools that will make your life easier and get things done easier, without having to thoroughly test new components, etc.

Also, if you were going to create something that you needed over and over, that's cool. You could also probably find that same something from a framework that's already been tested and running in many environments for quite some time. I just don't see the point of re-inventing the wheel, especially when you risk inventing a square wheel (untested code) that will take more time.

Don't get me wrong, if you enjoy creating your own stuff, cool. But to say that Frameworks are useless or are for people who can't write their own stuff, etc. -- that's just foolish and absolutely backwards. It's like trying to design and build a new hammer to hammer a nail when you've got one sitting right next to you. Time = money.

It's like watching a crazy guy call someone fools for using power tools to build a house, while saying he could build something better to get the job done quicker... fuck that shit. If you want to create stuff in Javascript rather than use jQuery, more power to you. But there's a reason jQuery was made.

I find it odd that we're on an Affiliate forum blasting automation (Frameworks).