![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Jun. 7th, 2005 11:42 amWell, there's a good thing about being at the end of a project- mainly that there's some downtime before things ramp up again. It's strongly suggested that we use that time to improve our skillsets. So, this week and probably at least some of next week i'll be sitting at my desk working through a book on writing ASP.Net code.
Rumour has it that there may be an opening for a junior developer coming open around the end of the summer, so this could be construed as taking steps in that direction; but at very least, it's having the opportunity to categorically demonstrate that some of the things which i've puzzled out about ASP.Net via following the logic chains are correct, and it'll make reading code that much easier.
One of the banes of my work existance- one of the travel club websites- is releasing a CMS version shortly- allegedly tomorrow. This will free me up from being that group's pet web developer— a role which got assumed for me when i offerred to make some text changes on the site because i was free at the time and the dev who'd usually have done so was slammed with other work items. It's not that i minded doing it, but that the turn-around time was usually unreasonable ("Oh, we have this new offer that needs to go out on the site today. You can do that, can't you?" while i was working on a project and juggling triage in wherever possible) and the content provided was never quite right, so even cutting and pasting what was submitted into the pages then needed at least one round of edits before it was good to go, which became a significant nuisance ("Get your stuff exactly the way you want it, and then send it to me, and i'll drop it onto the pages.").
Anyway, back to ASP.Net and C#.
Rumour has it that there may be an opening for a junior developer coming open around the end of the summer, so this could be construed as taking steps in that direction; but at very least, it's having the opportunity to categorically demonstrate that some of the things which i've puzzled out about ASP.Net via following the logic chains are correct, and it'll make reading code that much easier.
One of the banes of my work existance- one of the travel club websites- is releasing a CMS version shortly- allegedly tomorrow. This will free me up from being that group's pet web developer— a role which got assumed for me when i offerred to make some text changes on the site because i was free at the time and the dev who'd usually have done so was slammed with other work items. It's not that i minded doing it, but that the turn-around time was usually unreasonable ("Oh, we have this new offer that needs to go out on the site today. You can do that, can't you?" while i was working on a project and juggling triage in wherever possible) and the content provided was never quite right, so even cutting and pasting what was submitted into the pages then needed at least one round of edits before it was good to go, which became a significant nuisance ("Get your stuff exactly the way you want it, and then send it to me, and i'll drop it onto the pages.").
Anyway, back to ASP.Net and C#.
