I've have been looking at other laptops. All laptops have compromises. It used to be Apple compromise was the price, max heat/thinness, and the shiny screen. I've found plenty of laptops that have terrible keyboards, limited Linux support, no SSD, no PCI SSD, terrible trackpads, terrible screens, limited RAM, poorly thought out high DPI screens, even worse thermal management, touchbar-like gimmicks, etc. I won't buy a current MacBook Pro, and probably never again, but I haven't seen anything else I liked unreservedly, either.
I also reserve the right to complain about how the last decade of Linux Desktop development has gone to produce something that looks like but isn't as good as Windows 95, and how of my 4 most used Windows app, 3 of them quit differently and all have different chrome. Also how Haiku apps stutter, even though the multithreaded UI was supposed to prevent that.
I pointed out the total lack of security with such a password years ago while I was complaining that the FIOS install program managed to delete Safari bookmarks. People in the Verizon newsgroup laughed at me for caring about such a thing.
Before they fired me, we would hire people for a week or 2 week contract. I think this is much easier for both sides to manage than a milestone. I agree with some of the comments above. Having only the first win selects for the wrong sorts of traits. If you did the least amount of tasks because you were helping the other programmers, or adding documentation to the wiki, or identified and fixed one of the many core design flaws in the code, I'd still hire you.
My output included the comments (not that there were many) and used clearer function names where possible. And indented code. And added whitespace. It was far easier to read. Plus, editing PHP in ZDE is certainly easier than FGL in vi.
As mentioned, a translation doesn't help you comprehend the original intent, only manage the source with different tools. If you want to "bridge mainframe Cobol apps to the rest of the enterprise", one could slap a Java API on the COBOL. The COBOL->Java code may be incomprehensible to a Java programmer, but can be extended on a function by function basis with real Java.
Solution: automated language translation tools. I moved an app in Progress FGL to PHP. There was a lot of debugging as the original code had many different styles over the years, and I was aiming for automating only the easiest 99%, but I could have spent more time up front. One could write a COBOL interpreter, or even compiler for the JVM. It would require a compatibility environment, but from the comments here, COBOL doesn't seem to place too many demands on the OS.
If the problem is "nobody understands the original intent, only what it does now", admit you have no real control over the source and turn the whole thing over to a translator. You still won't have any control over the new source, but at least you can run it on Linux.
Easy answer: both keep the old platform and get a new environment. I converted a massive app in Progress's Fourth Generation Language (Clearly from the pre-Google era) into PHP/Postgres using Antlr. This allows modern tools and programmers, but still carries forward the thousands of undocumented changes and mystery quirks that the customers have come to know and love.
It might be worth noting that the pictures with the article on Japanese animation are a heavily edited revision done by Canadians, and a show done in America.
I will agree that "Cardcaptors" is much more violent than "Card Captor Sakura", but only because they (Nelvana, the Candians) removed every thing that suggests othewise.
Slashdot Mirror
I've have been looking at other laptops. All laptops have compromises. It used to be Apple compromise was the price, max heat/thinness, and the shiny screen. I've found plenty of laptops that have terrible keyboards, limited Linux support, no SSD, no PCI SSD, terrible trackpads, terrible screens, limited RAM, poorly thought out high DPI screens, even worse thermal management, touchbar-like gimmicks, etc. I won't buy a current MacBook Pro, and probably never again, but I haven't seen anything else I liked unreservedly, either.
I also reserve the right to complain about how the last decade of Linux Desktop development has gone to produce something that looks like but isn't as good as Windows 95, and how of my 4 most used Windows app, 3 of them quit differently and all have different chrome. Also how Haiku apps stutter, even though the multithreaded UI was supposed to prevent that.
I pointed out the total lack of security with such a password years ago while I was complaining that the FIOS install program managed to delete Safari bookmarks. People in the Verizon newsgroup laughed at me for caring about such a thing.
Before they fired me, we would hire people for a week or 2 week contract. I think this is much easier for both sides to manage than a milestone. I agree with some of the comments above. Having only the first win selects for the wrong sorts of traits. If you did the least amount of tasks because you were helping the other programmers, or adding documentation to the wiki, or identified and fixed one of the many core design flaws in the code, I'd still hire you.
More horrible than COBOL? :)
My output included the comments (not that there were many) and used clearer function names where possible. And indented code. And added whitespace. It was far easier to read. Plus, editing PHP in ZDE is certainly easier than FGL in vi.
As mentioned, a translation doesn't help you comprehend the original intent, only manage the source with different tools. If you want to "bridge mainframe Cobol apps to the rest of the enterprise", one could slap a Java API on the COBOL. The COBOL->Java code may be incomprehensible to a Java programmer, but can be extended on a function by function basis with real Java.
Solution: automated language translation tools. I moved an app in Progress FGL to PHP. There was a lot of debugging as the original code had many different styles over the years, and I was aiming for automating only the easiest 99%, but I could have spent more time up front. One could write a COBOL interpreter, or even compiler for the JVM. It would require a compatibility environment, but from the comments here, COBOL doesn't seem to place too many demands on the OS.
If the problem is "nobody understands the original intent, only what it does now", admit you have no real control over the source and turn the whole thing over to a translator. You still won't have any control over the new source, but at least you can run it on Linux.
Easy answer: both keep the old platform and get a new environment. I converted a massive app in Progress's Fourth Generation Language (Clearly from the pre-Google era) into PHP/Postgres using Antlr. This allows modern tools and programmers, but still carries forward the thousands of undocumented changes and mystery quirks that the customers have come to know and love.
http://assembla.com/ is pretty much what you are looking for. You can go in and see people as they work, or get an expert to build a team for you.
(Disclaimer: I have not used the site, but have worked directly with Andy Singleton)
Once "everybody" finds a site like rent-a-coder, quality drops through the floor, so I probably shouldn't be posting this.
I will agree that "Cardcaptors" is much more violent than "Card Captor Sakura", but only because they (Nelvana, the Candians) removed every thing that suggests othewise.