437 karma · joined December 11, 2010
Ellison can't beat that.
True, but the business context always changes. I doubt most of the payroll logic from 50 years ago is still in use today. Therefore someone needs to write new code, or change the old code.
> Many COBOL applications are large; rewriting them isn’t cost-effective—or even necessary.
Yes, your IBM sales rep makes sure of it.
E2N is developing SaaS for hospitality since 2009. We’re a small team of motivated, committed experts, looking for a proactive candidate to complete our Software Team.
Required skills: German C1, 3-4 years of experience as software developer, self-education
Tech stack: Java, MySQL, AWS, JSF
Benefits and perks: competitive salary, health insurance, company pension scheme, high impact work, modern hard- and software equipment, beach volleyball-, soccer- and basketball court, team events
More details and application: jobs.e2n.de
Not an expert in HPC, but I think you gain the performance from distributing the data across a vast number of cpu instead of having great cpus to begin with.
Forgive my ignorance, but that is the whole point of working with a relational database. If cannot use JOINS then this solves only a very limited use case.
It is always about how we use technology, not the technology per se. For the good, for the bad, for making money. Whatever.
Was it a HTML Gui with file upload and everything? Or just some server, port and proprietary protocol?
Maybe these things are on Ebay for cheap. Oh, that looks like fun.
I know as a software developer you don't want to do that. More fun refactoring code than dealing with management. More fun writing that piece of SQL than sitting in a meeting. Easier to whine about missing specifications than to understand the big picture.
Once I stepped back from coding and looked at the software from a birds eye view, I had actually a much easier time programming features than before. More knowledge, less writing code.