×
The Almighty Buck

Tech's Highest-Paid Engineers Are At Juniper 105

Posted by timothy from the fringes-matter-quite-a-bit dept.
Phoghat writes "The guys at Glassdoor have compiled a list of the 25 tech companies with the best salaries for software engineers. Google and Facebook made the list, of course. So did Apple and Twitter. But the company at the very top is a bit of a surprise: networking gear maker Juniper Networks."
Programming

Ask Slashdot: What Are the Hardest Things Programmers Have To Do? 473

Posted by Soulskill from the moderate-their-criticism dept.
itwbennett writes "Software development isn't a cakewalk of a job, but to hear programmers tell it (or at least those willing to grouse about their jobs on Quora and Ubuntu Forums), what makes programming hard has little to do with writing code. In fact, if the list compiled by ITworld's Phil Johnson has it right, the single hardest thing developers do is name things. Are you a software developer? What's the hardest part of your job?"
Programming

Has Flow-Based Programming's Time Arrived? 268

Posted by Soulskill from the go-with-the-flow dept.
An anonymous reader writes "Flow-based programming keeps resurfacing lately. FBP claims to make it easier for non-programmers to build applications by stringing together transformations built by expert programmers. Many projects have already been using similar approaches for a long time, with less (or different?) hype. Is it time to take a closer look at flow-based programming? 'Clean functions – functions without side effects – are effectively pure transformations. Something comes in, something goes out, and the results should be predictable. Functions that create side effects or rely on additional inputs (say, from a database) are more complicated to model, but it’s easier to train programmers to notice that complexity when it’s considered unusual. The difficulty, of course, is that decomposing programs into genuinely independent components in a fine-grained way is difficult. Many programmers have to re-orient themselves from orthodox object-oriented development, and shift to a world in which data structures are transparent but the behavior – the transformation – is not.'"

Slashdot Top Deals