|
|
|
| |
 |
| |
|
| |
|
|
|
I'm coming to the point of having to make a decision on something...
I started out building a CMS/templating/plugin system a few months ago in order to make my life easier when I start working on development for a living (still waiting for the visa, so unable to get paid for work right now) - things are going well with that, so I'm starting to think in terms of a release...
So, what licence?
1. Keep it proprietary
I could keep the system proprietary - there are a few advantages to this:[list][*]it gives me an edge when designing sites as I have the core system ready to be adapted to the customer's requirements (although with the glut of CMSs out there, this is only a slight edge)
|
|
read more | login or register to post comments
|
|
|
|
|
|
| |
|
| |
|
|
|
Some of the more astute (and probably older members) will recognise the ripoff title (there was a very bad game called "I Have No Mouth And I Want To Scream!" back in the early/mid-90s).
Anyway - the computer that I have all of my software on which I am using to make a CMS and some site designs on is a laptop. It is a laptop whose power socket no longer makes a connection to the jack... meaning that it won't power on...
This sorry state of affairs has been going on for a week - and while I do have a replacement part on order and in transit - I don't know when it will arrive. So, I have no computer! and I want to code!
|
|
read more | 3 comments
|
|
|
|
|
|
| |
|
| |
|
|
|
Okay, so you know that feeling you get once you've been doing this web development thing for a while, and you start up a new project, and sit staring at the screen wondering what the hell you're going to do and how you're going to do it? Well, I've been going through that the last couple of months...
Maybe my situation is a little exaggerated because of circumstances (I've had a whole major life transplant go on around me since Christmas - what with emigrating to a new country), but I think that everyone has gone through, or will go through, this at some point. I'd like to hazard a few strategies to get through the whole start of a project - whether its a simple website, a whole system (CMS or other), or any other kind of software project.
|
|
read more | 1 comment
|
|
|
|
|
|
| |
|
| |
|
|
|
It all started at the end of last week - I was trying to put some new functionality on my company's intranet (an SMS messenger service), and I hit a problem with my database interface: http://www.htmlforums.com/showthread.php?t=86317
As you can see, thanks to Vege, I was able to identify the problem - incorrect server version... So I got the all clear to down the box and install a new MySQL server.
Now, let me take you back almost three years. I was 24 then, just getting to grips with the idea that I was being trusted with developing a company intranet for an organisation of about 90 people. Trying to come up with all sorts of time and work saving code. I have to say that, in those three years I have learnt much and can now come up with a very good, robust, and easy to manage system.
|
|
read more | 2 comments
|
|
|
|
|
|
| |
|
| |
|
|
|
Whoa... 14 working days before I walk out of my office for good... kinda scary...
When I told my boss I wanted to go in mid-September, the end of the year seemed so far away. Now, I'm in crunch mode - mopping up the open support issues from the engineers in my company, along with finishing off some intranet functionality. And updating a price database for next year. And then writing a handover document for my boss and team-members to be able to do my job once I'm gone.
Still, despite the slightly elevated stress from having a very definite deadline ("So?" I hear most people ask "You're leaving, what do you care?" - well, I just don't like the thought of leaving unfinished business), I can't help but feel great that I'm getting out of here and moving on.
|
|
read more | 2 comments
|
|
|
|
|
|
|
|
|
|
|
|
