Maybe a "~19 year old college "bro" type" would be closer to the mark, given that the "brogrammer" label has been around for a while.
522 karma · joined July 16, 2010
Maybe a "~19 year old college "bro" type" would be closer to the mark, given that the "brogrammer" label has been around for a while.
I happen to work just up the road from your Crosslake office in the Liss building. Stop in if you're ever passing though.
Ideally it could be set up to configure and launch an emulator which would then build the code tree with the platform's native development tools (if needed).
Here's a concrete example:
1. Use emacs to write an AppleSoft BASIC program, myfile.txt"
2. C-x <run-on-emulator>
3. Automatically create a *.dsk file image, with the following files
a) PRODOS and BASIC.SYSTEM installed
b) a STARTUP program that executes the file, i.e.
10 PRINT $CHR(4);"-MYFILE.TXT"
4. Create (for example) a linapple configuration file to load this DSK image
5. Start the emulatorBUT ... there is only one hospital here and all of the doctors are part of the same system. So, although we could "comparison shop" for our physician, this had no effect on what we would (potentially) pay.
] CALL-151
* !
! 300: LDA 1000
David Schmidt has contributed a lot of free software to the Apple II community over the years and, IMHO, deserves recognition for his work by those that build upon it.
Just in the past few months, several SNES co-process chips that remained un-emulated for years, have been deciphered and fully emulated in BSNES. Without Byuu leading the charge into the last bastions of SNES emulation, I absolutely believe that some of these devices would be lost to history.
From my perspective, they did not implement it. Mark Miller and Robert Muir were able to implement the algorithm for the N=1 case, but were stuck until they found the existing Moman code. They did not implement their own code using Moman as a reference implementation, but just used Moman's code to generate the required tables.
From the article, "Not really understanding the Python code, and also neither the paper, we desperately tried to write our own Python code to tap into the various functions embedded in Moman's code". This sounds to me like they did not have a good understanding of the algorithms they were trying to implement.
They did do a fair bit of testing and did uncover a bug in the Moman code base, but, again, they did not fix this bug themselves, but appealed to Jean-Phillipe who then quickly fixed his code -- in effect, they were relying on a third-party.
And, yes, they did apply the end result to make fuzzy searching a lot faster, which is a good and practical end. It took a lot of effort on the Lucene's team part to get this feature implemented, but that does not mean that anyone has a good understanding of the end result.
In short, I don't get the impression that anyone on the Lucene team could give a 1 hour talk on implementing the Klaus Schulz and Stoyan Mihov paper to a formal language and automata audience.
If you want to maintain something close to your existing salary, you must at least look for companies or locations that actually pay that kind of salary to begin with.
This is probably quite obvious advice, but I think we (as developers) sometimes lose sight of the fact that there is not "one true salary range" for any particular set of skills.
* Subversion for source control
* Jenkins for building/testing/deployment coordination (each project has a Build, Push to Test Server, Integration Test Suite, and Push to Production set of jobs)
* NSIS to build installers
* Migrator.NET for database schema migration and rollback
* PsTools + NAnt + Robocopy + Misc. Utils to deploy to remove server
Our deployment process (managed by Jenkins), looks like this: 1. Pull code from SVN
2. Build the code
3. Run unit tests
4. Build the database migrations
5. Build the installer
6. Copy the installer to the test server
7. Use PsExec to run the installer
8. Copy back the install log to the build server
9. Build the integration test suite
10. Run integration tests (usually Selenium + NUnit)
11. Copy the installer to the production server
Final deployment is done from within Jenkins, too, but is a manual process for now. And by "manual" I just mean that someone has to click the "Run Job" button.Sure, it's not an "integrated" solution, but I don't really see how I'd have needed less control or granularity if I were building and deploying on Linux and didn't use Ruby.
Each 65816 opcode takes between 2 and 8 cycles to execute (more for the MVN and MVP opcodes) and there are rules about when interrupts can be asserted -- bsnes correctly emulates these processor details.
Also, I believe the bsnes properly takes into account the read and write states of the memory bus. This is also an intra-opcode level of detail.
AFAIK, some of the other CPU cores (esp. the DSP-n and Supergameboy cores) are straightforward opcode interpreters.
MVC.NET 3 + Entity Framework 4 + OpenRasta + Membership Framework + MEF + LINQ + dojo has been a good experience so far.