The Big Programming Thread - Page 314
| Forum Index > General Forum |
Thread Rules 1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution. 2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20) 3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible. 4. Use [code] tags to format code blocks. | ||
|
Roe
Canada6002 Posts
| ||
|
Craton
United States17274 Posts
"Hey I can't log in anymore?" "Oh, I accidentally cleared out the control table" | ||
|
heroyi
United States1064 Posts
On June 21 2013 10:44 Roe wrote: Sort of on the note of the last questions, what would be an average or exemplar day of being a programmer? From 9-5, what kind of things do you face? From what I understand alot of it is just debugging and maintenance until the job asks you to make a program that fulfills their desire (of whatever it may be). | ||
|
tofucake
Hyrule19188 Posts
On June 21 2013 10:44 Roe wrote: Sort of on the note of the last questions, what would be an average or exemplar day of being a programmer? From 9-5, what kind of things do you face? ![]() | ||
|
tec27
United States3702 Posts
On June 21 2013 10:44 Roe wrote: Sort of on the note of the last questions, what would be an average or exemplar day of being a programmer? From 9-5, what kind of things do you face? Well, I don't work 9-5, so there's that Today I came in around 11:30 and left around 9:30, although there was probably a good 2 hours in there where I was eating/talking to my co-workers about non-work related things. I spent probably half an hour to an hour reading email, about an hour reviewing other people's code, probably around 4 hours writing code, and maybe 2-2.5 hours trying to solve some issues with our build setup. I wouldn't say that's 100% typical of every day at work, but its fairly average. I have on average maybe 3 meetings a week, usually 30 minutes to an hour long. Some of my co-workers (especially the ones who have been there a while) have quite a few more.That probably won't be typical of a lot of companies, but don't settle for the ones where its not ![]() | ||
|
phar
United States1080 Posts
Last month? Maybe <5% writing code, <5% fixing bugs, 20% mentoring new interns (yay), and 70% fighting with productionizing a new product (boo) - instrumentation, monitoring, logs, chasing down powers-that-be to approve various logs stuff, blah blah blah I drew the short straw. Thankfully it'll be over "soon" and I can get back to actually coding.This will vary from company to company and team to team. If you have a lot of crappy legacy code where nobody is really sure how it works, you'll spend a lot of time fixing bugs. If you know the right questions to ask your interviewers, you can sort of get a rough idea of how much cruft they have to support. And then if you have options, you can not go to those places :p | ||
|
Craton
United States17274 Posts
| ||
|
nunez
Norway4003 Posts
so far in my summer job i am spending most of my time reading essays... written by mr mvsc... about templates and errors... | ||
|
Rotodyne
United States2263 Posts
Basically this guy has a Unfuddle SVN set up for source code management. I figured out how to use that, and can update the files. But I have no idea how to update the files on the test server so I can actually try to start the project. If someone could read the email I received below and tell me where to get started, that would be awesome. I am thinking I need to use putty? But I am pretty clueless + Show Spoiler + Thanks. Invitation to SVN Sent from Unfuddle (look for the email). Credentials for the testing server: OS: RedHat Domain: xxx.yyy.com root password: zzz Location of current version (There is SVN installed so you can use SVN to update/commit code from/to SVN server) /srv/public/xxx Please note the /srv/public/xxx/src/admin folder which is not at the SVN. This is a script that we use in order to allow editing the configuration file from the web. You don't need to commit it, change it or use it (only if you really want :-) Web access: URL: zzz.yyy.com You can update it from /etc/nginx/nginx.conf Don't forget to reload the nginx after changing the configuration file /usr/local/nginx/sbin/nginx -s reload Let me know for any question you may have Good luck :- ) | ||
|
BlueBoxSC
United States582 Posts
class Java { public static void main(String args[]) { System.out.println("Java is okay..."); } } | ||
|
3FFA
United States3931 Posts
On May 22 2013 11:03 vvSiegvv wrote: I'd highly recommend CS:193p taught via ItunesU with Paul Hegarty. All of the lectures you can get for free I believe off of Itunes, and it was a really well taught lecture series that my university incorporated into our own iOS development class. Hope this helps! Ok, I've started going through the Fall 2011 course. I'm curious, why doesn't NSString *digit = sender.currentTitle;work(it worked in the course video)? All the other dot notation shown in the 2nd lesson, the calculator demo, works. However, for this, XCode only accepts NSString *digit = [sender currentTitle];as it thinks sender is an undeclared variable if dot notation is used. Also, in what sort of cases would putting @synthesize brain; instead of @synthesize brain = _brain; cause a problem? | ||
|
Intgrl
27 Posts
But I'm not sure what should I focus on. I could just continue doing my own stuff with Java/Python while checking up new things when I need to apply them to my programs. Or should I just start learning C? Or is C too hard to learn at this point? I'm not really that interested in the theoretical side. I have access to uni courses but they really don't seem to be my thing (the 2 courses that I took are very different from the rest). I don't have the time to learn programming full time. So I'm not trying to become professional but I want to learn something useful and I want to write code instead of read books about the subject. So, in short, my question would be if I should continue learning Java/Python which I have enjoyed so far, or should I start looking at C (I know nothing about C). | ||
|
zeru
8156 Posts
| ||
|
WoolySheep
Canada82 Posts
| ||
|
adwodon
United Kingdom592 Posts
Seem to spend a lot of time on msdn and newsgroups trying to figure out what Microsoft's APIs do, then figuring out why they don't do it. A hell of a lot of time reviewing work before a check in, debugging / testing. Some time is spent doing support aka teaching professionals how to do their job, not indicative of all support though, I'm just a junior so I just get handed crap. Too much time fucking about on the interweb. | ||
|
nimdil
Poland3751 Posts
These times this pic is quite outdated as even big pieces of software frequently compiles in few minutes tops on modern computers (I guess there are exceptions but few). However if you work with databases (and I don't mean as in using it for storage dump for program but really working with the data) you can end up having tons of time waiting for the result of the query. Databases rule. | ||
|
nimdil
Poland3751 Posts
On June 23 2013 19:32 zeru wrote: I'd say every programmer should at least learn the basics of assembly and C, even if they are going to mostly work with higher level languages. The general coding knowledge in overall understanding of what the hell you are actually doing when you write higher level code is extremely helpful. I seriously doubt that knowing assembly will help you when doing Java - C is probably as low level as it's worth going to. I know I never really need to apply my assembly knowledge while working with Java/.NET programs. | ||
|
tec27
United States3702 Posts
On June 23 2013 20:23 nimdil wrote: These times this pic is quite outdated as even big pieces of software frequently compiles in few minutes tops on modern computers (I guess there are exceptions but few). However if you work with databases (and I don't mean as in using it for storage dump for program but really working with the data) you can end up having tons of time waiting for the result of the query. Databases rule.I spend probably an hour a day or more waiting for things to compile (usually I do other things during this time), and I have a 12 core Xeon and a hugely distributed build system. If you think that comic is outdated, you just haven't seen a codebase of sufficient size yet ![]() | ||
|
MaGariShun
Austria305 Posts
On June 23 2013 19:32 zeru wrote: I'd say every programmer should at least learn the basics of assembly and C, even if they are going to mostly work with higher level languages. The general coding knowledge in overall understanding of what the hell you are actually doing when you write higher level code is extremely helpful. From my experience as a java programmer and CS student I don't know how assembly or C would help you. I do know C (as a matter of fact I am programming a C++ VST Synthesizer plugin for my thesis right now) and have a basic understanding of how assembler works (couldn't write you a working program though), but never did that knowledge help me when programming in Java, Python etc. Knowing the basics of assembly is very useful when you are a C programmer, but for higher level languages, especially interpreted ones, It's really not necessary. Knowing C doesn't do you any good either when you are programming high level stuff. The only thing it teaches you is how pointers work and really, you can understand call by value/reference and how your specific high level language handles data types in that regard without studying C. My personal experience is that people starting out with C generally write very ugly code from a Object oriented perspective once they get to higher level languages. So I would say that the only time that knowing C and assembler really is useful, is when you have to actually use them (performance oriented applications) | ||
|
tec27
United States3702 Posts
On June 23 2013 19:18 Intgrl wrote: I took two uni courses to get started with Java (never programmed before). It went very well and I learned a lot. The courses were mostly just doing programming exercises and that's what I liked. After that I've been working on my own project. It's a simple quiz-type game with a simple GUI. I learned to use image files in my GUI and got more experience with reading/writing text files to store statistics or other data. I've also taken a look at python and I kinda like it too. So I'm still just a beginner. But I'm not sure what should I focus on. I could just continue doing my own stuff with Java/Python while checking up new things when I need to apply them to my programs. Or should I just start learning C? Or is C too hard to learn at this point? I'm not really that interested in the theoretical side. I have access to uni courses but they really don't seem to be my thing (the 2 courses that I took are very different from the rest). I don't have the time to learn programming full time. So I'm not trying to become professional but I want to learn something useful and I want to write code instead of read books about the subject. So, in short, my question would be if I should continue learning Java/Python which I have enjoyed so far, or should I start looking at C (I know nothing about C). I think knowledge of C can be useful, but I don't see why you'd go down that path right now. If you're just interested in programming as a hobby, just keep working on projects your interested in. The lower level knowledge is completely unnecessary for a hobbyist, and you will be able to make plenty of cool stuff without delving into it. | ||
| ||
![[image loading]](http://imgs.xkcd.com/comics/compiling.png)
Today I came in around 11:30 and left around 9:30, although there was probably a good 2 hours in there where I was eating/talking to my co-workers about non-work related things. I spent probably half an hour to an hour reading email, about an hour reviewing other people's code, probably around 4 hours writing code, and maybe 2-2.5 hours trying to solve some issues with our build setup. I wouldn't say that's 100% typical of every day at work, but its fairly average. I have on average maybe 3 meetings a week, usually 30 minutes to an hour long. Some of my co-workers (especially the ones who have been there a while) have quite a few more.
I drew the short straw. Thankfully it'll be over "soon" and I can get back to actually coding.