Jump to content

  • Log In with Google      Sign In   
  • Create Account

Banner advertising on our site currently available from just $5!


1. Learn about the promo. 2. Sign up for GDNet+. 3. Set up your advert!


cadjunkie

Member Since 28 Feb 2013
Offline Last Active Today, 09:33 AM

Posts I've Made

In Topic: What to do when your idea was already taken

29 June 2015 - 09:07 AM

The problem is that everyone's already thought of everything already tongue.png

 

I agree with everyone that you've basically got 2 choices, but I would also say keep developing. Sometimes during the development process you decide to make a few changes here and there that don't look like much, but they affect the overall product. Also, it's better to have something you can change or reuse if you have a sweet idea for a new feature later on.


In Topic: Are you the "From Scratch" type?

18 June 2015 - 03:58 PM

I am one of those types, but I like to call it a "not invented here" type.

 

It's not that I hate other people getting the credit or even think I'm better or smarter than they are. My reasons are about mainly about time savings. Generally, I know what I want to do and sometimes I don't think it's that hard building that thing from scratch. Usually there's a learning curve associated with the library/framework/etc. and I think I would spend at least as much time learning how to properly use the library (which often includes way more functionality than I'm looking for) as I would just coding the bits up that I need. As well, documentation is not always the best, leaving me to either have to read the source to see how they implemented function X, or just use it and hope it doesn't create more inefficiencies. I hate the latter option because it's the programming equivalent of pull-and-pray, so I usually try to go through the source. However, this doesn't extend to things like physics or rendering engines or something of that magnitude.

 

Like the OP says, why would I not just save myself the time and stop making more work for myself? I think for me, I like baking my own bread but raising and slaughtering my own animals for meat is too much.


In Topic: Engineering vs Programming?

17 June 2015 - 09:52 AM

 


IMO, if you make your hobby your job, it can get old fast.

To me, programming for my job and programming for my hobbies are so completely different that I don't really associate the two. One is not using up my mental capacity or my tolerance for the other. If anything, the hobby work recharges me for the pro work. It's kind of like reading and writing by this point: reading things and writing things at work has no relevance to the things I read or write on my own time. It's just a different form of literacy.

 

 

I can see how that would work. I just remember getting really into martial arts when I was younger and took over a studio from another instructor. I remember thinking I loved teaching and being able to make my hobby something that makes money was going to be great. And it was awesome...for like a month or two. It was tough to find the motivation and energy to teach some days. Those days came more and more frequently and it eventually became kind of a grind, so I passed it over to someone else.


In Topic: Engineering vs Programming?

16 June 2015 - 06:33 PM

I work in aeronautics as a structural engineer building large military UAVs. I can't really speak about software jobs personally but IMHO, aeronautical engineering isn't really as glorious as some people make it out to be. Sure, you get to work on some high-profile projects and use some fun software, but ask anyone in aerospace what they *actually* do and you'll usually hear something like "You know the X aircraft, right? Well on the wing there's a series of smaller Ys that do Z and I analyzed several of those" or "I designed the tooling fixture that locate the Ys on aircraft X". Sometimes you do get to do the "cool stuff", but that's usually not the norm and it takes a long while before anyone will trust you enough (i.e. promote you high enough) to design the important (read: cool) things. I personally like the challenges I get faced with and how much I'm learning, but that's not to say that software is any less interesting or challenging. Plus, unlike what your parents seem to think, aerospace engineers look at computers all day. CAD, simulation software, and Microsoft Office-type work is all we ever do, really (other than the other menial work of looking up specs or reading tech manuals online). Also, engineers aren't really people-persons. I'm an extrovert, but I have to go down to the shop floor to get any real human interaction (okay it's not all that bad, but you get my point). Also, more often than not, you're not going to be picking up a wrench or going into the machine shop and building anything. It's numbers work. That's why you get a higher salary than the shop guys. Plus, IMO, programming can be more stable. Aerospace is about having lots of money to do new things. It takes millions to build a simple airframe, so when the economy's good there's a lot of work to do. When it tanks (like in the US in 2008), there's a lot of unemployment. It's a roller coaster. The upshot is that stuff has to get made even in a down economy, so usually there's something in consumer products you can find work in. I'm not trying to make this sound unattractive, but just paint things a bit more realistically so you can get a better picture of what the choice looks like.

 

I love to develop software (mostly mechanics simulation software) because of the problems I get to try to solve, but I couldn't ever see myself doing that professionally. IMO, if you make your hobby your job, it can get old fast. Sure, some days you'll love to go to work and get excited about it, but on the days you don't want to do it, you have to force yourself to do it. I like to unwind by thinking about something other than work, which programming lets me do. However, it's obvious that enough people love it more than I do that they've made their career doing it. It's really all about what you'd rather do all day.


In Topic: What Do You Think Of Micro Apartments ?

16 June 2015 - 05:58 PM


living in one of those micro-apartments really does require that you are fairly disciplined with regard to keeping the place cleaned as well tidy or you quickly become buried in your own filth

 

I'll bet it didn't take much time to clean though, given there's not much area to clean :-)

 

I think the idea might be good for people who honestly don't spend enough time at home to justify shelling out hundreds to just have sleep in a place, but I really think this is just a ploy for building owners to increase profits further. The only way you could possibly increase your bottom line more is if you leased this same apartment to 2 people, one person working days and one working nights.


PARTNERS