Become a fan of Slashdot on Facebook


Forgot your password?

+ - How Java Changed Programming Forever

Submitted by snydeq
snydeq writes: With Java hitting its 20th anniversary this week, Elliotte Rusty Harold discusses how the language changed the art and business of programming, turning on a generation of coders. 'Java’s core strength was that it was built to be a practical tool for getting work done. It popularized good ideas from earlier languages by repackaging them in a format that was familiar to the average C coder, though (unlike C++ and Objective-C) Java was not a strict superset of C. Indeed it was precisely this willingness to not only add but also remove features that made Java so much simpler and easier to learn than other object-oriented C descendants.'

Comment: Re:Quite the Opposite (Score 4, Insightful) 266

by Rasperin (#49745841) Attached to: Ask Slashdot: Career Advice For an Aging Perl Developer?
There's a difference between a team lead, architect, PM, and an IT manager. The IT manager strives to learn and understand but basically manages the team, the PM translates the coders and works between them and the business. The team lead needs to understand everything and the architect needs to understand the code capabilities and the bigger picture.

Here the guy listens, learns from those under him but has the previous technical insight and the business experience to be able to respect the iron triangle and the business while being able to manage money and his department. But hey don't listen to me on these definitions, this is just my experience. (I'm sure I'll get a bit of flame for even suggesting this)

Though I guess if you haven't ever had a manager role I'd say go PM. But as real advice I'd say read up on modern JS techniques and go in as a front end developer at say a php shop or any shop that separates their front end guys from their back end guys. JS esp. things like node are making a rather big break through imho.

Comment: Re:You're dying off (Score 1) 284

by Rasperin (#49721499) Attached to: The Auto Industry May Mimic the 1980s PC Industry
In bigger cities with decent public transportation but in cities (like Kansas City or it's outlying suburbs like Johnson County) cars are the only way to get around. Walking and biking isn't practical when the closest McDonalds is over 7 miles away in the suburbs (not that we are apparently eating McDonalds anyways). Sure there is a mythlogical bus system that some believe, nay have faith!, exists but it's quite elusive and won't get you near your destination.

I'd think anywhere that's not east coast/west coast in the united states still will have a demand for vehicles (exclusions also count outlying islands, I only add this part because someone will call me out on it. I'd say this counts chicago too but I don't know if they ever got their shit together and made a decent public transit system).

+ - The Auto Industry May Follow in IBM's Footsteps->

Submitted by Anonymous Coward
An anonymous reader writes: An article at TechCrunch looks at some interesting parallels between the current automobile industry and the PC industry of the 1980s. IBM was dominant in 1985, employing four times as many people as its nearest competitor. But as soon as Windows was released, the platform became more important for end users than the manufacturer. Over the next decade, IBM lost its throne. In 2015, we're on the cusp of a similar change: the computerized car. Automakers, though large and well-established, haven't put much effort into building the platform on which their cars run. Meanwhile, Google's Android Auto and Apple CarPlay are getting better and better. As soon as those hit a breakthrough point where it's more important for a customer to have the platform than the manufacturer's logo on the side, the industry is likely to look like a replay of the PC industry in the 1980s.
Link to Original Source

Comment: Re:No. (Score 1) 507

by Rasperin (#49698903) Attached to: Is Agile Development a Failing Concept?
Actually that's my favorite and technically I believe how scrum is supposed to operate. If changes come in, then the rest of that sprint (or the next sprint) is supposed to be to designing and making said changes and getting them approved. Then after the design sprint it begins development sprint the following (or a future one depending on what is going on). Point is Agile is supposed to be agile to the buisness and the developers but be realistic and not cowboy coding.

Comment: Re:nVidia (Score 1) 158

by Rasperin (#42266813) Attached to: Frame Latency Spikes Plague Radeon Graphics Cards
I just went over to the Radeon because of the multimonitor support given off of one card. I have 5 monitors attached to my current video card and I like it that way. Before then I bought nVidia because they worked so well without issues. I have had multiple issues from radeon since purchasing it, but oh well I finally got it to work.

If I have seen farther than others, it is because I was standing on the shoulders of giants. -- Isaac Newton