|
It was a sad day when towards the end of life of the Amiga, they changed that text. :C
|
|
|
|
|
Write something that interests you. Games, graphics, sound. Whatever it is that holds you interested.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Quote: someone has already done it and better than I could do it
If that's true, maybe you should hang up your keyboard.
On the other hand, it's not about the destination, it's about the journey.
|
|
|
|
|
Decide on a project that interests you, even if there isn't necessarily a 'need' for it by others.
Two projects I plan to complete are:
First, a .NET based clone of a game I wrote back in high school on a Commodore PET - the game was, by nature of the platform, keyboard based. Now, I have other input options - mouse based with button to click instead of keyboard commands; better graphic options, possibly even sound (but, considering me, I doubt it)
Second: a platform to track dependencies - forward and backwards from a starting point; that means I need to have an input mechanism, a search mechanism and a reporting mechanism. I've toyed with the idea of having a graphical representation of the output and being able to limit (or not) the number of predecessor and successors to an item.
|
|
|
|
|
You've got to look forward, to the future.
Make a power-governor for lightsabres.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Well, according to the story line in Rogue One: A Star Wars Story, he will need to harvest some Kyber Crystals if he is going to do lightsaber work. Don't know if we have any on this planet.
|
|
|
|
|
That's hardware. Leave that for the mechanical engineers to screw up.
The software's worth making a start on now, though.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Pick one:
ByteStruck[^]
Beta is 90% complete, just need to finish the matching algorithms.
FlowSharp[^] and FlowSharpCode[^]
I'm doing some really cool things with FlowSharpCode (which is now actually merged into FlowSharp) and of course there's a large TODO list (see Issues section) in FlowSharp itself.
Projourn (sorry, no public link), a project journaling web app (much like a blog, but also different.) Some initial work has been done, including REST services and a WinForm client to play around with prototyping.
Marc
|
|
|
|
|
Wow, that ByteStuck site looks like the type of site I was looking for a few days ago
i cri evry tiem
|
|
|
|
|
James_Parsons wrote: that ByteStuck site looks like the type of site I was looking for a few days ago
Exactly. Hence the reason for creating it.
Marc
|
|
|
|
|
Is this your site?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: Is this your site?
Certainly. I wouldn't post a link to something that wasn't mine!
Marc
|
|
|
|
|
What are you using on the backend?
i cri evry tiem
|
|
|
|
|
James_Parsons wrote: What are you using on the backend?
My own web server (no IIS dependencies, nor is it ASP.NET / Razor.) I haven't written about the web server back end much, but the code is open source[^]. ByteStruck itself is not open source.
Also, SQL Server Express, hosted on an Amazon EC2. Core web "frameworks" are jQuery (of course), jqWidgets, and Knockout.
Marc
|
|
|
|
|
Oh, and I forgot, Bootstrap as well, like everyone else.
Marc
|
|
|
|
|
OK. Looks promising.
When I go to Projects/Jobs = > View Public Projects/Jobs
or
Projects/Jobs = > Geek Matches
I get "Route not found"
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Kevin Marois wrote: I get "Route not found"
Indeed - missing implementation. I actually usually don't have the server running, I fired it up actually when I wrote my original reply, haha.
Marc
|
|
|
|
|
Collaborate on a project. Code to www.codeplex.com and find a project that interests you and get involved.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Well, Windows has already been done, but I don't think you'd have any problem doing it better.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
James_Parsons wrote: I have not touched any code for 6 months
James_Parsons wrote: it looks good to employers
Um, er, why haven't you touched code in 6 months? Reason why I ask is because you mention this fact in the same paragraph as the word "employers". I would not hire you if you haven't touched code in 6 months without a very, very good reason.
Just curious.
|
|
|
|
|
Haha, I guess it doesn't matter I wouldn't get hired anyway . I'm an 18 year old kid straight out of high school with little experience living in one of the worst states for the industry.
I haven't touched code in 6 months because after graduating, I had no more projects to work on.
i cri evry tiem
|
|
|
|
|
College plans? Military plans - non-combat, with technical MOS (programming, etc.)?
If you love to code then you need to show an employment timeline with full-time coding, software development, etc. I would focus more on that then side projects, IMHO. I don't consider people for employment based on their "side projects".
|
|
|
|
|
Quote: College plans? Military plans - non-combat, with technical MOS (programming, etc.)?
Actually, I recently failed to get into the Army, Now trying the Air Force.
i cri evry tiem
|
|
|
|
|
James_Parsons wrote: Now trying the Air Force.
Air force or Navy is best for technical jobs. I would start with Air Force.
If you go military, then go non-combat MOS (Mission Occupational Specialty) and pick a speciality that you know will help you get employment when you get out (i.e. software development, etc.)
I was in the Infantry but if I had to do it over again, I would go Air Force.
Good luck.
|
|
|
|
|
James_Parsons wrote: I've also tried the whole "make something you would use" and wind up finding out someone has already done it and better than I could do it.
I agree with the idea of making something you would use. This is very practical advice. My best 'side projects' have been little utilities that I now use just about every day both on or off the job. There's sure to be at least one small utility application you currently use that could be just a little better...maybe a better UI or an added feature or two. Start from scratch and/or use samples/examples from working code (with proper credits of course!) to make something that you can get immediate results from and improve on over time.
"Go forth into the source" - Neal Morse
|
|
|
|