I hope you realize you aren't left out of the loop, only left out of the negotiation panel. I would much rather get something done then have to wait for approval I don't need if it's not going to break anything. That entire issue with the forum slaving was a disagreement in how to add more forums without killing the entire thing, I wanted redundancy, you wanted 'now'.
You're wanting 'now' is what pisses people off when you come into the middle of things and meddle where you weren't asked to, or form a conclusion without knowing all the answers.
I don't want this to turn into good cop/bad cop, with you always portrayed as the bad cop. Take a look at ComicGenesis History and see how it is almost always you taking unilateral action AND getting the flack for it.
I'll be honest and admit I've been leaving you behind in development matters because I don't want you even trying to fix anything I write, because when you do, it gets broken worse. There are three rules I try to abide by in coding: 1. Write bug-free code (always fix warnings) 2. Write secure-first code (always initialze variables, validate everything) 3. Write flexible code (no throw-away code, a lot of perl stuff uses the same framework)
Nowhere in there is "document clearly" or "get approvals from 15 layers of management"
So this means that in Perl, always using use strict and -w, in PHP this is turning on the debugger and making sure there are no warnings, ever. PHP is a lot more difficult to get bug-free code since there is no defined output. It either works or you get the white screen of death.
I experiment a lot and only put in code that I know works. Sometimes it outgrows it's usefulness like the last version of the newsbox. Sometimes it was written for one thing and got used somewhere else (the ENTIRE database backend was designed for the GUIDE originally.)
What really pisses me off is when you decide to do something that has a major effect on ComicGenesis and people complain. I always put a poll in the forums to see if people even want said feature if it's going to be significant. Check out the newsbox size poll, I opted to implement all the sizes anyways (as different ad caches), but the 150x300 image size is still the newsbox size. There were times where you were saying that you were going to change the size to the keenspot size and I was like NO we aren't, and you still repeated it.
I even remember back when I proposed half of this DB design for a new database backend, when nate actually did something on the server, and we agreed to use a new backend... and nothing became of it. So not everything I want to do ever works. There was the experimental help.keenspace.com that didn't work (The wiki was a much better idea), there was putting the jams in the wiki, that didn't work. There was the javascript flatfile newsbox that didn't get used by more than three people, there was a bunch of utilities I wrote in shell script and perl when we still had the flatfile backend that people used and I wound up throwing them away because they weren't adaptable to the database.
The FIRST program I ever wrote that used a database is a perl program to automate changing the forums and tying it to the keenspace account... guess why this never was released? Because I wanted the database backend for keenspace at the time and the flatfiles were easily destroyed.
So using the forums as the main "author-user" database was part of MY plan all along, and I would still throw this all away if I could write everything from scratch.
In fact It wouldn't be too far fetched to just write a dozen different updaters... you know HTML3.2, HTML4.01, XHTML, XHTML+CSS,XSLT, AJAX, etc and let the user use. I'm all for choice. I converted most of the existing Autokeen to have both XHTML and XHTML+CSS versions of tags so people could do some customization, something I wanted to back before I EVER did anything with keenspace. You might say my having anything to do with keenspace was being in the right place at the right time.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
syntheid
no subject
Date: 2006-01-24 10:50 am (UTC)You're wanting 'now' is what pisses people off when you come into the middle of things and meddle where you weren't asked to, or form a conclusion without knowing all the answers.
I don't want this to turn into good cop/bad cop, with you always portrayed as the bad cop. Take a look at ComicGenesis History and see how it is almost always you taking unilateral action AND getting the flack for it.
I'll be honest and admit I've been leaving you behind in development matters because I don't want you even trying to fix anything I write, because when you do, it gets broken worse. There are three rules I try to abide by in coding:
1. Write bug-free code (always fix warnings)
2. Write secure-first code (always initialze variables, validate everything)
3. Write flexible code (no throw-away code, a lot of perl stuff uses the same framework)
Nowhere in there is "document clearly" or "get approvals from 15 layers of management"
So this means that in Perl, always using use strict and -w, in PHP this is turning on the debugger and making sure there are no warnings, ever. PHP is a lot more difficult to get bug-free code since there is no defined output. It either works or you get the white screen of death.
I experiment a lot and only put in code that I know works. Sometimes it outgrows it's usefulness like the last version of the newsbox. Sometimes it was written for one thing and got used somewhere else (the ENTIRE database backend was designed for the GUIDE originally.)
What really pisses me off is when you decide to do something that has a major effect on ComicGenesis and people complain. I always put a poll in the forums to see if people even want said feature if it's going to be significant. Check out the newsbox size poll, I opted to implement all the sizes anyways (as different ad caches), but the 150x300 image size is still the newsbox size. There were times where you were saying that you were going to change the size to the keenspot size and I was like NO we aren't, and you still repeated it.
I even remember back when I proposed half of this DB design for a new database backend, when nate actually did something on the server, and we agreed to use a new backend... and nothing became of it. So not everything I want to do ever works. There was the experimental help.keenspace.com that didn't work (The wiki was a much better idea), there was putting the jams in the wiki, that didn't work. There was the javascript flatfile newsbox that didn't get used by more than three people, there was a bunch of utilities I wrote in shell script and perl when we still had the flatfile backend that people used and I wound up throwing them away because they weren't adaptable to the database.
The FIRST program I ever wrote that used a database is a perl program to automate changing the forums and tying it to the keenspace account... guess why this never was released? Because I wanted the database backend for keenspace at the time and the flatfiles were easily destroyed.
So using the forums as the main "author-user" database was part of MY plan all along, and I would still throw this all away if I could write everything from scratch.
In fact It wouldn't be too far fetched to just write a dozen different updaters... you know HTML3.2, HTML4.01, XHTML, XHTML+CSS,XSLT, AJAX, etc and let the user use. I'm all for choice. I converted most of the existing Autokeen to have both XHTML and XHTML+CSS versions of tags so people could do some customization, something I wanted to back before I EVER did anything with keenspace. You might say my having anything to do with keenspace was being in the right place at the right time.