An anonymous reader writes "A German computer scientist is taking a fresh look at the 46-year old Amdahl's law, which took a first look at limitations in parallel computing with respect to serial computing. The fresh look considers software development models as a way to overcome parallel computing limitations. 'DEEP keeps the code parts of a simulation that can only be parallelized up to a concurrency of p = L on a Cluster Computer equipped with fast general purpose processors. The highly parallelizable parts of the simulation are run on a massively parallel Booster-system with a concurrency of p = H, H >> L. The booster is equipped with many-core Xeon Phi processors and connected by a 3D-torus network of sub-microsecond latency based on EXTOLL technology. The DEEP system software allows to dynamically distribute the tasks to the most appropriate parts of the hardware in order to achieve highest computational efficiency.' Amdahl's law has been revisited many times, most notably by John Gustafson."
Find out the latest on data centers with SlashDataCenter.
BorgeStrand writes "I'm reviving an open source project and need to read up on a lot of existing code written by others. What are your tricks for quickly getting to grips with code written by others? The project is written in C++ using several APIs which are unknown to me. I know embedded C pretty well, so both the syntax, the APIs and the general functionality are things I wish to explore before I can contribute to the project."
mpol writes "We're all aware of PRISM and the NSA deals with software houses. Just today it was in the news that even Microsoft gives zero-day exploits to the NSA, who use them to prepare themselves, but also use the exploits to break into other systems. At my company we use Git with some private repositories. It's easy to draw the conclusion that git-hosting in the cloud, like Github or Bitbucket, will lead to sharing the sourcecode with the NSA. Self-hosting our Git repositories seems like a good and safe idea then. The question then becomes which software to use. It should be Open Source and under a Free License, that's for sure. Software like GitLab and GNU Savane seem good candidates. What other options are there, and how do they stack up against each other? What experience do people have with them?"
itwbennett writes "You can make a decent living as a software developer, and if you were lucky enough to get hired at a pre-IPO tech phenom, you can even get rich at it. But set your sights above the average and below Scrooge McDuck and you won't find many developers in that salary range. In fact, the number of developers earning $200,000 and above is under 10%, writes blogger Phil Johnson who looked at salary data from Glassdoor, Salary.com and the Bureau of Labor Statistics. How does your salary rate? What's your advice for earning the big bucks?"
So far, the Rails Girls have groups in cities ranging from Warsaw to Wellington, with U.S. gatherings in Washington D.C., Charlotte NC, San Francisco CA, and... let's make it easy: Here's a map. OMG! They're everywhere! Actually, mostly Europe, being as they started in Finland, same as the Leningrad Cowboys and a popular computer operating system. But they're spreading like mad. Would you believe the reason one of the two founders originally got interested in Ruby on Rails was because she wanted to make a fan page for American politician Al Gore? Our interviewee, Magda (from Rails Girls Warsaw), swears this is true. She also tells us about their upcoming Washington D.C. workshop on June 13th, 2013, in conjunction with the June 14-15 RubyNation event. Sounds like fun, doesn't it. Maybe you need more of this kind of fun where you live, eh? If there isn't a Rails Girls group near you, maybe you should start one and help more women and girls get into programming. This is the Rails Girls' goal. Any particular ages? Not really. And their workshops are all free of charge: "You just need to be excited!"
An anonymous reader writes "I have had an interesting situation arise where I built some web apps for a client about 2 years ago. I have no longer been working with the client and a new developer has taken over purely for maintenance work. Currently I have been looking for new work and have used the said apps as part of my portfolio. During one interview I was informed that I not telling the truth about building the apps and I was then shown the source of a few JS files. It seems the new developer had put a copyright header on them, removed my name as the author and put his own. Now this is grey territory as it the client who owns the source, not the contracting developer. It put me on my back foot and I had to start explaining to interviewers that the developer stole the work and branded it. I feel it makes me look like a fool, having to defend my position in an interview with a possible client and I feel I had lost the chance of directing the outcome of the interview. I have cut the apps from my portfolio, however they are some of my best work and a real testament to my skills. I decided to cut my loss and move on, I am not looking for a fight or any unnecessary heartache. So what you do in my situation?"
aarondubrow writes "For more than 50 years, linguists and computer scientists have tried to get computers to understand human language by programming semantics as software, with mixed results. Enabled by supercomputers at the Texas Advanced Computing Center, University of Texas researchers are using new methods to more accurately represent language so computers can interpret it. Recently, they were awarded a grant from DARPA to combine distributional representation of word meanings with Markov logic networks to better capture the human understanding of language."
theodp writes "It was the best of movies; it was the worst of movies. GeekWire reports that The Internship — the new comedy starring Vince Vaughn and Owen Wilson as two 40-something guys who get internships at Google — is getting high praise from Googlers but low marks from movie critics. Google CEO Larry Page called the movie 'a lot of fun' in his Google+ post, while fellow Google exec Vic Gundotra gushed, 'I laughed a lot while watching this movie!' After screening a sneak preview with Google companions, Wired's Steven Levy wrote, 'From Google's point of view, the movie could not possibly be better.' USA Today's take, on the other hand, is that 'Google has never looked lamer thanks to The Internship.' And the NY Daily News calls the movie 'an unfunny valentine to Google.' But perhaps the unkindest cut of all comes from the NY Post, who suggests that 'maybe The Internship was secretly funded by Bing.' Ouch." Update: 06/07 20:02 GMT by T : Peter Wayner saw the movie (a "harmless bit of summer fluff"), and his full-length take below takes on some of the tech-company misconceptions that the film-makers gleefully adopted as script material.
Nerval's Lobster writes "In the early 2000s, three young programmers without much money gathered in a basement and started coding what would become one of the most widely used pieces of software in the video game industry. 'Nobody really remembers how we survived in that period except we probably didn't eat much,' said David Helgason, the CEO and co-founder of Unity Technologies, maker of the Unity3D game engine. A decade later, untold numbers of developers have used Unity3D to make thousands of video games for mobile devices, consoles, browsers, PCs, Macs, and even Linux. The existence of Unity3D and similar products (such as the Unreal Engine and CryEngine) helped democratize game development, making the kinds of tools used by the world's largest game companies available to developers at little or no cost. This has helped developers focus less on creating a video game's underlying technology and more on the artistic and creative processes that actually make games fun to play. In this article, Helgason talks about how Final Cut Pro helped inspire his team during the initial building stages, how it's possible to create a game in Unity without actually writing code, and how he hopes to make the software more of a presence on traditional consoles despite Unity3D being several years late to supporting the PS3 and Xbox 360."
The Next Web reports that GitHub — home to many open source projects — suffered (and quickly recovered from) a service outage this morning, starting around 14:00 UTC. Other than that the problem "appears to have been caused by its database server," the cause isn't clear.
theodp writes "In The Unexotic Underclass, C.Z. Nnaemeka argues that too many smart people are chasing too many dumb ideas. 'What is shameful,' writes Nnaemeka, 'is that in a country with so many problems, with such a heaving underclass, we find the so-called 'best and brightest,' the 20-and 30-somethings who emerge from the top American graduate and undergraduate programs, abandoning their former hangout, Wall Street, to pile into anti-problem entrepreneurship.' Nnaemeka adds, 'It just looks like we've shifted the malpractice from feeding the money machine to making inane, self-centric apps. Worse, is that the power players, institutional and individual — the highflying VCs, the entrepreneurship incubators, the top-ranked MBA programs, the accelerators, the universities, the business plan competitions have been complicit in this nonsense.' And while it may not get you invited to the White House, Nnaemeka advises entrepreneurs looking for ideas to 'consider looking beyond the city-centric, navel-gazing, youth-obsessed mainstream' and instead focus on some groups that no one else is helping."
Trailrunner7 writes "Bug bounty programs have been a boon for both researchers and the vendors who sponsor them. From the researcher's perspective, having a lucrative outlet for the work they put in finding vulnerabilities is an obvious win. Many researchers do this work on their own time, outside of their day jobs and with no promise of financial reward. The willingness of vendors such as Google, Facebook, PayPal, Barracuda, Mozilla and others to pay significant amounts of money to researchers who report vulnerabilities to them privately has given researchers both an incentive to find more vulnerabilities and a motivation to not go the full disclosure route. This set of circumstances could be an opportunity for the federal government to step in and create its own separate bug reward program to take up the slack. Certain government agencies already are buying vulnerabilities and exploits for offensive operations. But the opportunity here is for an organization such as US-CERT, a unit of the Department of Homeland Security, to offer reasonably significant rewards for vulnerability information to be used for defensive purposes. There are a large number of software vendors who don't pay for vulnerabilities, and many of them produce applications that are critical to the operation of utilities, financial systems and government networks. DHS has a massive budget–a $39 billion request for fiscal 2014–and a tiny portion of that allocated to buy bugs from researchers could have a significant effect on the security of the nation's networks. Once the government buys the vulnerability information, it could then work with the affected vendors on fixes, mitigations and notifications for customers before details are released."
itwbennett writes "If you've ever worked on a team you can probably recall a time when, as a group, you produced work that was not as good as any one of you could have done on your own. Sarah Mei had this sort of sub-par teamwork experience, which she shared in her session at the O'Reilly Fluent Conference this week. Mei 'spoke about a time she worked on a team with really expert developers. Every one of them was someone whom you'd admire, who had previous written code that you and I would boast to have created. Yet, these smart people created modules that didn't talk to each other. And its quality was, to be kind, on the rotten side.' It's not an uncommon story, but why and how does it happen? The answer, says Mei, is that code quality 'is defined by its patterns of dependencies,' not all of which have equal weight. And, as it turns out, team communication is the heaviest dependency of all."
AvailableNickname writes "I am currently pursuing a bachelor's in CompSci and I just spent three hours working on a few differential equations for homework. It is very frustrating because I just don't grok advanced math. I can sort of understand a little bit, but I really don't grok anything beyond long division. But I love computers, and am very good at them. However, nobody in the workforce is even going to glance at my direction without a BSc. And to punish me for going into a field originally developed by mathematicians I need to learn all this crap. If I had understood what I was doing, maybe I wouldn't mind so much. But the double frustration of not understanding it and not understanding why the heck I need to do it is too much. So, how important is it?"
plutoclacks writes "I will run a computer science club at my high school next semester with two other friends. The club was newly introduced this school year, and initially saw a massive success (40+ members showed up at the first meeting). Unfortunately, participation has decreased a lot since then, down to four active members. I feel that the main reason for this decline was the inability to maintain the students' interest at the beginning of the year, as well as general disorganization, which we hope to change next semester. The leaders of the club all have fairly strong Java backgrounds, in addition to enthusiasm about computer science and programming. We have a computer lab with ~30 computers, which, though old, are still functional and available for use. What are some ways we can make the club have an impacting interest to newcomers?"
theodp writes "'Every programmer likely remembers how they learned to code,' writes GeekWire's Taylor Soper. 'For guys like Bill Gates and Paul Allen, the magic began on the Teletype Model 33 (pic). For others, it may have been a few days at a coding workshop like the one I attended for journalists.' If you're in the mood to share how and in what ways your own developer days began, Soper adds, 'cyborg anthropologist' Amber Case is collecting stories to help people understand what it takes to learn how to code. Any fond computer camp stories, kids?"
New submitter NeoHermit writes "This language (Dao) has never been mentioned on Slashdot before, but it might be interesting to many people here. As it has recently become feature-complete and just made its first beta release, it may be the right time to mention it here. Dao is an optionally-typed programming language that supports many advanced features with a small runtime. The feature list is probably as long as that of Python, but they are supported by a much smaller runtime (somewhere between Lua and Python, but closer to Lua). Besides optional typing, the other major features that worth mentioning include: built-in support for concurrent programming for multicore computers, very friendly C programming interfaces for embedding and extending, a LLVM-based JIT compiler, a Clang-based module for embedding C/C++ codes in Dao, and a Clang-based tool for automatic binding generation from C/C++ header files. You can also see many familiar features from other languages."
blackbearnh writes "Most commencement speeches are long on platitudes and short on practical advice. O'Reilly blogger James Turner has tailored a speech aimed specifically at the current batch of graduating CS majors. Among the advice that the 35-year industry veteran offers are to find a small company for your first job, but not one that is going to burn you out. Also, keep learning new things, but don't fall into the trap of learning the flavor of the day technology. Quoting: 'Being passionate about software is critical to being successful, because the field is a constantly moving target. What will net you $130K today will be done by junior programmers in five years, and unless you're constantly adding new tools to your belt, you’re going to find yourself priced out of the market. ... You are rarely going to get an opportunity to have your current employer pay for you to learn things, so learn them on your own and be in a position to leverage the skills when a new project comes along. But if you have a passion for technology, you'll already be doing it, and enjoying it without needing me to tell you to."
An anonymous reader writes "I really want to go travel the world with the money I've saved up at my day job, but I also want to grow as a developer in the process. This is a long-term engagement: 2-3 years or more depending on whether my software is successful. I'll probably be hopping from hostel to hostel at first, with a few weeks at each. How do I find a good work environment in these conditions? Do hostels generally have quiet areas where work could be done? Is it OK to get out your laptop and spend the day in a cafe in Europe, assuming you keep buying drinks? What about hackerspaces — are those common on the other side of the globe? (Apartments are an option for later on, but I'm concerned about losing the social atmosphere that's built in with the hostel lifestyle.) I've never done anything like this before, but I'm really excited about the idea! Any advice would be greatly appreciated."