Forum Replies Created
-
Posts
-
Well, to be percectly honest, I could go for a couple of 12 hour coding sessions. Although, I'd have to be seriously motivated to do it anymore. After spending all day coding at work, sometimes the last thing I want to come home to is more coding. Although I have my moments where I just want to work on the site, kinda like last night…which reminds me, I need to finish what Im doing and post a frickin update.
I think we should seriously consider using both XHTML and CSS in our pages. Neither of which are incredibly difficult to pick up. Ive got a basic (very basic) knowledge of CSS. XHTML is just a combo of HTML and XML, or if you want to look at it this way, a stricter version of HTML, because of the way they make you have closing tags. Its really not a bad way to go in my opinion.
I can certainly guarantee that we will definitely get more done if we have some free time and plenty of cold pizza, combos and pop. (That summer was so awesome, wasnt it, a T1 all to ourselves)
Also, if we really want to get a lot of this stuff done, we have to be organized. Not only in our coding, but with everything else as well. Im trying to write some PHP functions that we'll use a lot, that way we dont have to constantly re-write them. I really need to get you a basic tutorial of PHP, I think it would be useful to you. I dont know how busy you are now, so you'll have to let me know so I know when I can work with you on it. I have to tell you, it would be nice to have some help in this development. After 12 hours or so, my brain gets cooked…
Found some more info that will be helpful. http://www.htmldog.com. Run through both the HTML tutorials, as well as the CSS tutorials. They'll both be incredibly helpful. The HTML is all done in XHTML, in case you're wondering
Let either of us know if posting something on the website would be useful for you. Im sure Greg wouldnt mind
putting something up to showcase some of your abilities in finding work. Or if you just need space to build,
doesnt really matter. Just let either of us know and we'll get you fixed up.
Try to keep track of the changes you're making, just in case. Ive been backing up the site
about every week or so, but it never hurts to keep track of that type of stuff.
Ok, perhaps we either need to rethink the smakk domain name, or
just incorporate it directly into Mightor Industries. I have no problem with either solution.
Danny, get in touch with me and maybe we can work something out to at least temporarily house SMAKK at MI until we
figure out what we're gonna do with it, unless you prefer to use the Attic's hosting to house it.
Either way, doesnt matter. Let me know how I can help.
I just came across a sweet article from Slashdot about Microsoft not allowing a backdoor for the Vista
OS. This is exactly the idea Microsoft needs to be taking. I like seeing Microsoft taking a better
stance on security. We'll see if it actually pays off when Vista is released.
This is a good article and there's a lot of useful things mentioned in the article that I mentioned
in my previous post. however, Im not sold on the super fetch. It seems to me to be just another level of
paging, bringing things into the cache. The one thing I forgot to mention last night is that the perfect OS
shouldnt not take up a bunch of system resources. This seems to be the biggest problem for operating systems
nowadays. XP required more system resources in order to operate, and Vista will be no exception.
Ive been keeping an eye on it here and there, but then there's the whole thing about time.
Right now, all of my time is tied up in work stuff, so Im hardly on any news sites or doing any of my own
programming. Plus, I think my laptop is on the fritz. Just ordered a new computer today, as a matter of
fact. I have to have something operational, so I broke one of my own rules and purchased a prebuilt computer
with an intel chip. Before anyone decides to ridicule me over my selection, keep in mind that I have to be
able to work. I cant afford to build a new computer at the moment.
I'll post specs later.
I also saw one on there last night where a guy completely sealed up his system, and instead of it being
water cooled, the entire case was filled with oil! Apparently, it keeps the system pretty cool.
Although, it would be a pain and messy upgrade if you ever wanted to change anything, or would need to replace
anything.
Greg, thats a sweet idea for the book. Let me know how it works out.
Sounds like the
prof knows what he's doing, or at least from the way it sounds. I dont know about commenting the sections
of code apart, seems like a waste of space to me. Although, in a language like python, it might be useful,
especially when you're declaring variables. Another good idea is to keep a section of history for major
updates. I do this with my SQL code all the time (especially lately). It comes in handy when you're
trying to track changes to a script that usually doesnt get changed often, but that needs to have a comment here and
there. Its good to have a history of comments so you know whats been changed and when it was changed.
Function comments are incredibly useful as well. Remember that when programming, you're actually writing
for three audiences: the computer (you're writing code that the computer can understand), the user (you're
writing code so that a user can actually use it) and to other programmers (including yourself). The last one
is incredibly important. As I mentioned in my last post, keeping comments helps when you come back to a
project after not working on it for a significant amount of time. I find that a lot of programmers dont
comment their code and if they do, its a one liner that doesnt make any sense. There's no shame in
writing a couple of well thought out sentences saying what something does. You dont need to go overboard (I
went to school with someone who went crazy with the comments). However, you should write enough so its clear
on what is happening in your code. Also, and I know a lot of people, including myself, do this from time to
time, but comment prior to writing code. If you're getting ready to write a piece of code, add a comment
saying what it does. Sometimes, and I did this a lot in college, people will write their code then go back and
add comments when its finished. But by the time you're finished, you may not remember why you did
something a certain way.
If you couldnt tell, Im kinda picky about comments. One other thing
Im kinda picky about is indentation and formatting. In Python, you're forced to indent, but in other
languages, like HTML and C, you can write one long line of code. Anyone who's done HTML has see the one
line complex web page that you open in notepad and you see one long line with a tiny scroll bar that goes on for
miles. This is NOT good. Going back to the programming for other programmers, it makes it incredibly
hard to maintain code when you cant read it easily. Sure, I can decipher a one liner program, but what I
usually end up doing is formatting it first so its easier to read before I even attempt to start to understand
it. This is a waste of time in my opinion and should be avoided. Either that or force everyone to
program in Python 🙂
Maybe there's a reason why Walsh wont let me teach programming? I
picked up on too many of my advisiors habits and I tell you, they pay off. He was particular but in my
experience, its the only way to be, especially if you want to be a decent programmer. You have to be attentive
to detail, otherwise, some issues you'll never figure out. Like the stray semicolon in your C, C++, Java
or PHP code.
I lost track of my posts, I think this is 48.
