skysight-inc/HackerNews huggingface dataset:
Found a PDF for this one thanks to Google Scholar

4. T. Menzies and M. Shepperd, “Special Issue on Repeatable Results in Software Engineering Prediction,”
Empirical Software Eng., vol. 17, no. 1, 2012, pp. 1–17

http://menzies.us/pdf/12stability.pdf

EDIT:

Several of the author's articles are available here (click the PDF links):

https://www.simula.no/people/magnej/bibliography?b_size:int=...

From looking at Google Scholar it looks like there are many newer articles on Software Estimation that the OP does not reference so may not have read.

Edit 2:

This paper talks about Monte Carlo Simulation:

https://www.simula.no/research/se/publications/Jorgensen.200...
Very similar in spirit, but still different in the details. Dual numbers use nilpotent infinitesimals (which are not invertible), while non-standard (Robinson) infinitesimals are not nilpotent and are invertible.

That being said it's way easier to construct nilpotent infinitesimals using intuitionistic logic than it is to construct the hyperreals using classical logic.
* Solid advice from csmdev--
Managers want to know how you think. Might add in describing your results, include how your solution impacted the bottom line by helping to save the company money or increase revenue. It shows you understand the big picture and care about the larger business needs.
As a foreigner living here in Germany, I have been continually surprised by the level of regulation that is in place here.

I am often doubly surprised when I realise that nearly every single piece of legislation I've come across actually seems to make sense, when someone takes the time to explain it to me.

I personally think that the regulation of public transport is a good thing. The fact that people are insured when they transport me around in a 1 tonne potential deathtrap is a good thing.

The last thing I want to hear when I wake up in hospital gravely injured is "sorry sir, you'll have to sign here to accept liability because the driver of your unlicensed taxi wasn't insured to transport paying passengers".
I know I won't be popular with this comment and most likely downvoted, because Uber is so beloved (especially in Bay Area circles). But here it comes:
Why do people support a single company (like in this case Uber) taking over the business of thousands and thousands of existing companies and hence monopolizing an industry?

In most European cities, taxi companies are small, almost mom-and-pop entities with anywhere between one and say twenty taxis. In fact where I am living now I can call 4-5 different ones all in my vicinity. If there was an app that consolidated the booking process for those - awesome!

But why would there have to be a company that owns the market globally - from Karachi to Karlsruhe, from Amsterdam to New York, taking 20%, killing competition by it's pure überstrong market presence, brand and financial backing.

The same people that hate Comcast for oligolopolizing it's market (and hence using it's almost-monopoly powers for their benefit) yet somehow wish Uber would succeed and take over the market around the world. Why? Because it's a hip SF 'startup' (if you can still call an entity with $1,500,000,000 in funding a startup)?
Obama admits the US secret alliance with Iran
Pricing is a big interest of mine (30,000 words into writing a guide on it). Understanding your ideal pricing depends upon understanding your customers and your value proposition.

We need more information before we can tell you what to charge and how to charge it.
nice ad hominem assmunch
At least in this case, there are a lot more eyes and attention on cracking OS X Keychain compared to this browser extension which most will forget about in a week or so.
I would build a general profile of the application and then drill in as needed rather than try to grok the whole buffet at once.

If the idea is to rebuild the application I would start at the beginning: what is the input and output? What does the user see? What are the various service hooks? How are they called? When are they called? Why are they called?

Then I would look at how the overall code is organized. What modules are there? Are there core utility modules that seem to be called by everything else? What are those doing? What are the most used business function modules?

Then I would look at the build process. What external dependencies are there? What are they used for? Are there modern alternatives? What about internal dependencies? Does the build process look organized and sane or a chaotic mess cobbled together over the years?

Do you have logs? What is the most utilized part of the application?

Then I would look at the database. What tables seem to be the most important (if you could get usage stats from a running and used application that could help, but otherwise you could look at which tables are keyed off of the most)? What data is most critical? What modules interact with that data? What tables are essential for supporting this data?

Answering these questions will start to fill out a nice 30,000 ft view of the application and how it is actually used.

You are going to get the most bang for your re-implementation buck by identifying and replacing often used utilities (especially if they are custom built or built before a good de-facto standard was formed for that particular task) with modern, well known, alternatives. Then follow the execution path of the most often used modules and the modules that work with the most critical data and work down the list.

With a 100 million line application, you are looking at many years to understand all of it and many years to re-implement. To get anything useful in a reasonable amount of time you are going to have to boil it down as much as possible, then break what's left down into independent functional areas and tackle it an area at a time.

The code is important, but if it were me, I'd try to analyze how the users and processes work before I'd dig into the nitty gritty of the code too much if at all possible. I'd build the smallest functional unit from what I deem to be the most important and critical module(s) trying to cut as much cruft from the application and database as possible. I'd get users and processes to start banging on the new app as soon as possible. I'd keep the old application up and running and available to analyze (not for the users but for the developers and analysts) as the team works down the most often used parts. I would not try to analyze the whole mess in one go beyond finding waypoints as described above. If possible I'd also try to get users to understand that the old way is not necessarily the right way. Much pain has been caused trying to make new systems work exactly like the old systems when the new systems don't face the same constraints. It is just too tempting to say 'make it work like it did'.
Sounds like the premise for a good article. Not, however, this article unfortunately. This article instead throws out a handful of straw-men and chiefly complains that agile doesn't help you with software design, something it's never claimed to do.
Not that I'm against improving vector graphics, but The majority of images on the web today are not suited for vector formats (photos).
How secure is Windows Phone 8.1? Very
It builds under Mingw32 as well, and at least an earlier version built with VC++ without modification (I don't have access to a windows machine right now to verify). It also builds under Plan 9, which uses a very old and basic C compiler very far from C99.

Some of the optional extension libraries like networking may not work out of the box, but TinyScheme doesn't have these anyway.

Basically, Chibi was designed as a better TinyScheme. It's just as small, can also easily be included statically without a library, has a nicer (optional) FFI, various features like full Unicode, full numeric tower and hygienic macros (all optional), and is an order of magnitude faster.
Same and /second. I'd add that I've trouble encrypting emails with attachments, as Javascript encryption performance in web-based email in a browser that's being abused with lots of other tabs open is not always so reliable. Surprise surprise.

The Stanford Javascript Crypto Library whitepaper provides probably the best performance baseline for all of Javascript crypto [1], and the best they can do is roughly 10x faster than the next fastest JS crypto implementation, but still over 40x slower than native crypto.

[1]:http://crypto.stanford.edu/sjcl/
They were available as Fortran, LISP, C and Pascal were all around back then. But you're right about the necessity code the ROMs in Assembly .
The Singularity Is Near: When Humans Transcend Biology by Ray Kurzweil
This comment is the most well written response in this whole debate for all I can see. Thanks a lot.

It's a shame that it currently buried about 10 pages deep at the time of this writing, because it's a reply and not a top-level comment.
Conferência Internacional de Simulação de Edifícios 2014
There are mobile clients for KeePass databases. So you just need to keep a copy of your database on your phone. That's extremely easy to do with syncing data apps like SpiderOak.
> 100M lines of java code developed 'line-by-line'

If it's not generated, then it may be "versioned" that way. I saw projects where the entire codebase was copied over to new directories tens of times, and no previous "version" was ever deleted.

But, after giving it some thought, 100 mloc is really MUCH, like in 50x more than anything I directly worked with. It does sound kind of improbable, but hey, it could happen :)
Are you also looking for interns ?
Uber are lying liars who lie in many markets.

This is demonstrated by the fact that in London, they simply went out and got the PHV license, and made sure the vehicles comply (checks every 6 months, public liability insurance, etc.) - if they did this in every other market, no problem.

The issue is that isn't a very sexy business. It's not "disruptive" like car pooling.

And in some markets, the cost of complying with the regulations is extremely high.

Even in London, it's been argued that the app in the car is a meter, and therefore breaches legislation relating to metered trips: only black cab drivers are allowed to meter, and the regulation bar there is much, much higher in part because those drivers are free to just pick people up off the street without pre-booking.

It seems to me that they should either focus on ride-sharing and get out of the private hire business, or they should focus on the private hire business and do it properly.

The regulations around private hire are not some idiot state actors nannying around: in London they have evolved over centuries. Literally. They are constantly reviewed, and London has an incredibly diverse and active PHV market with many innovators (Addison Lee, Hailo, Kabbee, etc.) improving things in regards to customer choice.
Location: Santiago, CL

Remote: Yes

Willing to relocate: Sure! (US, Canada, Europe)

Technologies: Ruby(Rails/Sinatra), SQL (MySQL, Postgres), DevOps technologies(chef, vagrant, aws), html/js(jQuery/Angular)/css. Currently learning node

Resume: http://lnkd.in/zbp-q7

Email: castillo85 at gmail dot com

I've been working as backend developer and devops recently. I'm proficient in Ruby but interested in working with other languages. Also I'm open to work in different roles rather than backend developer and devops.
The consciousness article is from last year.
Pre Manstrual Tension is a bitch
Entrepreneurship is Juggling – for aspiring entrepreneurs
Report: US Foreign Assistance Detailed Data 2002 – 2012
TenFourFox dev here [:spectre on Bugzilla]. Yes, we run on 10.4. The best reason to still own a Power Mac today is Classic. It's why I do.

We track ESR and occasionally backport later fixes. It was easier to do it that way than to have widget or gfx break on rapid release -- that way we have the entire ESR cycle to get it right.

10.4Fx does have a JIT. Right now it's a highly modified version of BaselineCompiler (I hacked BaselineIC to have better type and shape guards that take advantage of the greater ILP possible with the PPC integer unit), but I've had trouble getting our JaegerMonkey implementation to come into the Ion age. What we'll probably end up doing is blowing it up and rewriting it based on MIPS, since MIPS does many of the same things we have to and is much more like us than ARM (they do lui/ori to load 32-bit quantities, we do lis/ori; they have a link register too; they have similar branch stanza requirements). We have an unusually large stack as well, mostly for the stack frame requirements of the ABI. I hope to have this ready by 38ESR.

Security is a concern for the browser. I hate relying on security by obscurity, but as you say, we're a tiny segment of a tiny segment (while 10.4Fx will run under Rosetta, and some crazy people do, it's not our core concern). We don't run Flash or Java anymore because of Rosetta Flash and Flashback, or any other plugins, for that matter. Since Firefox implements NSS, that means we're not beholden to deficiencies in the Apple-shipped SSL or NSURL. Heck, since Mozilla implements its own media libraries, we don't have to rely on the system ones either. It's going to be a lot safer than a Webkit shell which has all of those dependencies and more.

PowerPC forever.
Thats a very valid concern. For SmartOS it would be a major blow if Joyent were to pull all ressources. They have some of the brightest engineers I know working on it and I have learned a lot from them by just using the system and hanging out on the irc channel in freenode.
Without them the speed of development would definitly take a hit.

On the other hand they have been - and still are - very good at building a community around it. There are multiple people and organisations building their own SmartOS images/derivates ([1], [2]). Pull-requests on github come in from a diverse enough group that I think it would survive even without joyent.

For OmniOS I don't have enough insight to make that judgement. They have a very clear and detailed release plan and recently hired some good people just to work on OmniOS. These things definitly add some confidence but of course is not a guarantee forever. But if that would be needed one can always buy support from them.

[1] http://www.dogeos.net

[2] http://imgapi.uqcloud.net/builds
9 Simple Email Hacks to Increase Open Rates
One interesting side effect of this capping is that it is cheaper for me to phone a number on my home network while roaming, than it is when I'm in the country on the same network!

Three Ireland Prepay account mobile calls 35c/min, roaming calls 19c/min.
Do you not trust the OSX Keyring because of apple? Or outside attackers?

If it is apple you don't trust in this regard, keychain is the least of your problems.

If it is outside attackers. At least they should need physical access to the machine to crack it, right? (If you don't back up that specific keychain to iCloud)
Not my experience with batch files / shell scripts, but that's hardly any evidence.
Orbi: A little mouse and a super easy way to prove the Pythagoras Theorem
Net Neutrality: Join the Fight with Namecheap
Or keep using it anyway. Most organisations don't actually receive direct Microsoft support/assistance when they run into problems anyway. So Microsoft ending XP support is practically meaningless.

At worst, it allows independent software vendors a small market for regular repeat business. At best, people just keep using XP the same way they've been doing for years.
The thing you have to understand, 80k USD is a very very very high salary for most people (even developers) in Europe. And the ones that make that can most likely see 1/2 of that go away in taxes/social security. Cost of living will probably be higher than the equivalent salary in the USA.

On the other hand, people should get unemployment benefits when situations like this occur, unfortunately for him, the moving countries may have prevented that (for Sweden employment agency, he quit his Swedish job, not fired, and for Portuguese one, he didn't work enough months to qualify. I'm sure there are some international provisions for these situations but they are beyond me).
The guys who wrote the agile manifesto are also the same guys who created and promote Scrum though.

They kinda are one in the same.
> You should be as nice as you can to everyone, but pragmatically speaking you can't. There isn't enough time, money, or energy available.

Being nice to someone isn't the sum of all time, money and energy expended on someone. It's just treating them with respect and dignity when your path crosses with theirs.
I though this was the quarterly "why agile sucks" post on HN but instead it seems to list bad habits worth avoiding in effective agile teams.

If your agile consultant is promoting any of these myths you need a different one.
> something this magnitude

Yeah, I started commenting before the realization of how HUGE this thing would be hit me, sorry :)
I would disagree that the majority of images on the web are photos. Yes, there are many photos on the web, but I'd wager the vast majority of images (or at least the vast majority of image requests) are tiny bits of connective tissue of web layout - little rounded corners, gradient backgrounds, icons, etc.
It's not the users’ fault but if nothing else his IT department is being recklessly negligent by choosing to block security updates.
Private keys are not fungible, if you lose one you're done, game over. By putting them in more places you're making yourself strictly less secure.

Also, with that old and worn proverb about eggs and baskets, if having none of your eggs is equivalent in value to you for having only some but not all (i.e. you must have exactly all of them, or else you fail), then putting them all in one basket is better than putting in two (or more).
Mindless duplication shouldn't be a part of any software project, full-stop. It takes only slightly more time to refactor code into functions than it does to copy and paste, and the difference in comprehensibility is massive.
I think that's ultimately what I mean. As an example, compare this screenshot of my site[0] with css and Javascript on to this screenshot[1] with it off. It's still perfectly usable, even if it doesn't look nice. But the same basic structure of the page is evident, and it's not like things are suddenly jammed together or messed up.

[0] - http://nacr.us/media/pics/screenshots/screenshot--07-32-57.p...

[1] - http://nacr.us/media/pics/screenshots/screenshot--07-33-31.p...
But I think there is a difference. IE6 was so far away from the standard that you had real difficulty supporting both, and really couldn't embrace a lot of features other browsers supported well. This was of course by design, intended to keep us from moving away, but it was so rubbish that designers moved anyway.

IE9 in contrast is pretty decent. In fact it's perfectly fine for most sites. For me, it's Chrome that is now aggressively pushing its own agenda. It doesn't really concern itself with standards any more than IE did, but because it's open source, nobody really notices.
There's a bit of discussion over on DesignerNews (https://news.layervault.com/stories/32423-uilang--a-minimal-...)
with a link to Shorthand which is similar, but seems a little better to me (uses <script> tags and clearer language).

http://splatcollision.github.io/shorthand.js/
One peculiarity of batch files, and how cmd.exe executes them is that they are being read over and over (or maybe they are simply mapped file).

I've found this by trial-and-error - while I was editing a batch file that was executing, it would suddenly error out with meaningless info, sometimes it'll print out the things I've just added to it.
It's not worthless, and neither is "watching shit scroll by for hours", but I think the better signal is in the motivation and tenacity of the kind of people who set out to do this in the first place. In the 80's, this kind of people made up a very large proportion of all computer users out of sheer necessity (heck, in the 70s, you generally had to assemble your own hardware as well). Today, it's a vanishingly small fraction - but in absolute numbers, it's much much bigger, and a much much easier group to enter.
Footage from drone shows construction of new apple campus
I don't think kids should learn to use cutlery at such early age, not without proper ethics training. Cutlery gives you a lot of power. The power to do both good and evil. Children just don't have that kind of judgement.

If you teach a kid to eat with a knife and fork and they end up stabbing someone, who is going to take responsibility? Does the kid get tried as an adult or juvenile?
Don't try to figure out how the code does what does yet.
Figure out what systems exists inside it:

1. What kind of modules?
2. Which servers/hardware?
3. Which databases/datastores?
4. What systems talk to what?
5. What test systems exist or existed?
6. Which api/frameworks where used?
7. Who is currently working on them/maintaining it?
8. Is anyone left who used to?
9. Why is a rewrite on the table?
10. Is there any way you can work on smaller pieces at a time?
11. What are the pain points of the current users (will tell you what area to focus on)?
12. Can you document what comes in and out?

In my experience with such large code bases, there is never one way to do things. i.e. I once worked on a smaller system with 4 ways to talk to the same database. On one with 100 million lines I would expect even more ways to rome ;)

If you do want to go down the static analysis path, start with existing tools before trying to build your own. If needed get external help for this.

A 100 Million lines of code is not so bizarre. The project I work on is currently about 300,000 lines and a project some 300 times larger is quite imaginable for me.
I think the drivers themself would have to operate at a loss.
But they also have an exemption for ambulances. Maybe they can offer medical services for their clients. ;)
Tribler makes Bittorrent anonymous with built-in Tor network
Quicksilver - Neal Stephenson

http://en.wikipedia.org/wiki/Quicksilver_(novel)