skysight-inc/HackerNews huggingface dataset:
I've been trying to find good material on software development in an enterprise setting in the 'real world' not the magical world of unicorns and pixies you nicely described.

If anyone knows any good sources shout out.
Previously: https://news.ycombinator.com/item?id=15378422
کوه راشمور بنایی ملی در امریکا
کوه راشمور یکی از بناهای ملی در امریکا محسوب میشود. این کوه جالب و دیدنی در نزدیکی شهر کیستون در ایالت داکوتای جنوبی آمریکا در تپه هایی با نام تپه های سیاه قرار دارد
I liked the old butter pat design but the new zigzag is pretty slick. I could go with either, especially since I don't see icons anymore now that I use i3 + rofi
For a glimpse of that, this interview with a responsible for System Health Management for NASA rockets is interesting: http://omegataupodcast.net/100-system-health-mgt/
They have to start somewhere. It sounds like this will be an initial rollout.

Obviously they won't be limited to Chandler Arizona forever.
The old one was also not as neat as the Visual Studio equivalent. That’s why I made my own and changed from the "get info" menu of Mac OS. But each update override that icon again so I got fed up of changing it each month.

The new one is puzzling: it looks like the Visual Studio icon (which is still nowhere near as beautiful as the 2010 version), but the left part is missing. Is it a subtle way to tell that Code is an incomplete VS product?
Depends on the product but indeed I want stability over all else with updates for security. We have a product sold to us 2 years ago and still hasn't passed UAT. It is enterprise and they use agile so after every 3 to 6 weeks we get a new build to verify. There is always something new that fails so we go back to waiting. At this point I wish I could write the thing ourselves as I would have been done 18 months ago.
Yeah... but it is at least slightly funny seeing how angry the internet has got about this. I must admit, I do agree with the basic sentiment of the bug report though: the new icon is pretty fuggers.
Show HN: Oag – Idiomatic OpenAPI Go client code generator
Damn, that sounds like way more fun. I really missed out!
Methodologies are a trap. The problem with any methodology is they tend to lead people to stop thinking about the context they are operating in.

"The methodology says X, we should do X, why oh why aren't we doing X?" is a familiar lament in the development world. I have been there and done that, to be sure.

It really isn't going to matter what the Methodology says, if something or someone in the context means it isn't being adhered to.

If the person ultimately paying for the project isn't convinced by the Methodology, or wants to deviate from it badly enough, guess what? The Methodology will be ignored.

You should always advocate for what the Right Thing To Do(tm) is, but you should ask yourself first: what is the most important criteria that determines what the Right Thing is?

Sometimes writing the quickest, hackiest, throwaway code can be the Right Thing. It can be a horrifying truth for a software developer. Sometimes doing the ballsy re-write is the Right Thing. Sometimes letting a project fail is the Right Thing.

Sometimes last weeks context and decisions no longer apply.

More critical to project (and personal) success than any Methodology is gaining a thorough understanding of the context in which you are working in, as quickly as you can. And then doing all the Right Things that will make you effective within those constraints.

This means there is no Single Truth for software development. No easy answers. But there are a wide variety of principles you can draw from and apply and discard as needed.

Or as Bruce Lee put it: Be like water.
The style he describes as RAD is really enjoyable to work in. No constant scheduled meetings and unread documents; just use your common sense and write something.
Been using my tt-rss instance and Fiery Feeds on my iphone for a while now. Fiery Feeds does some magic to get the full articles in case they only display preview snippets.
I've been pure C developer for 5+ years (worked with codebase of ~2.5 million lines of code) and I took a quick look (just out of curiosity) at the content and one thing immediately strikes me:

http://cs.yale.edu/homes/aspnes/classes/223/notes.html#What....

7.1 What's wrong with C

a) C doesn't have a garbage collector

Disagree that's it's wrong. If you code is well structured, then it's no big problem to avoid memory leaks. On top of that, you can use RAII if you are willing to use C-extensions like this one:

https://lwn.net/Articles/589433/

Garbage collector just helps you to write semi-workable messy code (a dream of industrial developers).

b) C doesn't support any kind of polymorphism

If you use type cast in well structured code, it's no big problem.

c) C doesn't have exceptions

This may be a bit tricky but you still can use exceptions in C using longjmp/setjmp:

http://www.di.unipi.it/~nids/docs/longjump_try_trow_catch.ht...

Although __cleanup__ extension doesn't work in this case.

It's worth to take a look at this stack unwinding library:

http://www.nongnu.org/libunwind/

Quote:

With libunwind, it is possible to implement an extremely efficient version of setjmp(). Effectively, the only context that needs to be saved consists of the stack-pointer(s).

In general, if you look at C as a high level assembler and willing to write or use existing low-level framework for "meta-language" primitives (like pointer virtualization), then you can write nice programs in your "meta-language".

For example, I wrote some project for fun using pure C with bare minimum libraries. And I needed to make sure that I could detect the following bug as soon as possible:

1. Object X is created and owned by some code OWNER_X;

2. Pointer to this object X is passed to some code USER_OF_X;

3. Object X is freed in OWNER_X;

4. New object Y is created in OWNER_X which happens to have the same address as recently freed object X;

5. Because of some bug USER_OF_X still uses pointer to object X;

I wanted USER_OF_X to fail on asserts as soon as possible if this happens. It would be hasty bug and hard to detect in unprepared code if X and Y happens to be the same type. When people are saying that it's nearly impossible to detect such bugs in C, they just don't consider using framework which cleverly detects this issue.

By the way, this is my implementation pointer virtualization which helps to detect this sorts of bugs:

https://github.com/hal9000xp/euclid/blob/master/core/main.h

Look at PTRID.

https://github.com/hal9000xp/euclid/blob/master/core/linked_...

Look at usage of PTRID in LL_CHECK

This is how I use them together:

https://github.com/hal9000xp/euclid/blob/master/core/network...
Switch to the insider version it has better logo. It is green.
> It uses the phone's audio jack and Bell 202 modem-like FSK encoding with up to 1225 bit/s.

That seems very low, considering that there is solid wired connection between the two endpoints. Even actual modems pushed bits way faster than that, and PSTN transmission quality is much worse.

I suppose this is hampered by the fact that Arduinos do not have proper DACs, but still I wonder how fast you could use something like libquiet https://github.com/quiet/quiet on a Arduino.
> "It was fairly clear in our survey that people note cash carries more degree of privacy over non-cash items. And that was one of the key reasons people said they will continue to use cash in their transactions."

WORKSFORME

Though I am generally happy with electronic transactions, and was founder and CTO of an e-money firm, I do not want my every move and activity tracked directly/indirectly via banks. The data will leak from time to time and the results will be messy. Cash allows the insertion of data firewalls into activities.

One of the motivators for the previous company was to provide some anonymity for transactions, eg buying a present for your other half that would not show up on shared accounts, or, equally, buying sex toys or whatever. That motivation is still good. (No, just for the record, neither of those use cases applies to me right now!)
Well, it's not the main problem. Just a new problem, therefore gathers new attention. The main problem people have with it is the resource usage, as it's built with Electron.

There's an abundance of text editors available and there's generally only minor differences between them, so people will weigh up those minor differences all the more.
Why Orange when the editor's main color is blue? Does not look right.
If they do it right, the user doesn't have to care. You call a car, and either a self-driving or a non-self-driving one will show up, depending on the trip you selected.

But that's for the future; for now I'm pretty sure every car will have a driver, even if just as a backup/supervisor.
Something like Scrum springing up is completely predictable though
The Single Truth about software development is that there is only one deliverable: working software.
I have to agree, VS2010 had the most beautiful icon of any Microsoft IDE.
Nest and Google Home are on the market. They meet the definition of robot, but fall into the same problem the parent mentions.
Parliaments operate based on rules with a central authority, usually called the speaker, who acts to settle disputes. Parliaments do not operate like an extended family.
It really is. Is there somewhere I can download the old icon and some way that I could use it as a replacement? (I'm on Linux; Ubuntu with Gnome shell specifically.)
Every military and intelligence outfit has their own mapping unit why is this exactly surprising?

The only reason why these maps gathered any attention is that funny enough they were actually use by some western companies as they were effectively either very cheap or without any royalties at all while most western maps are a copyright hell that would cost you a fortune to even look at.

The article also seems to glance over a lot of the inaccuracies that ended up in the soviet maps including made up places from movies and other popular culture.
Musescore.com is showings ads
That doesn't actually guarantee no funny business, someone could jump into the middle of a multibyte instruction. Generally speaking games shouldn't be doing that so it should be fine, but there's nothing stopping it. It does however show the problem that you can't always actually tell where some code starts within a block.

Note: I'm not talking about the Xbox specially. Its binary format my actually make it clear where every piece of code starts, or there may be other ways of telling.
Great post. This is a very clear explanation of the routing situation. The last image is especially good.

What's needed is some kind of L2 Traceroute. It's maddening that an increasingly common piece of routing infrastructure is invisible to almost all common troubleshooting tools.

Edit: Cisco has one for their routers [0]. Since each hop would have to be traced locally, an L2 Trace would require orchestrating against all hardware devices in the route which introduces legal complications. A new discovery protocol might be needed.

[0] https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6...
Oh, you know, I'd forgotten about the paper airplanes and pasta sculptures.
What’s worked best for me is basically ‘agile’ but without a lot of what I consider to be the bullshit. Project manager and/or team lead prioritize new cards as they come in, and developers just keep working on them. No sprints, just keep pulling work out of the backlog as needed. Stand ups and most meetings can be replaced with quick updates via Slack, otherwise they can be organized as needed (they usually aren’t). We had agreed that estimation was mostly a pointless waste of time, so we stopped doing it.
Waymo has hundreds of vehicles logging millions of self driving miles on the road. They have plenty of data.

Tesla's "tunnels": I assume you are referring to elon's Boring Company? How many decades of tunneling do you think that will require before it even covers a fraction of routes people want to take?
In general I agree with you, but that assumes that you have people (and management) with the sufficient big picture thinking. I have found that it is usually safer to follow methodologies even if they aren't perfect because the alternatives are worse when dealing with average or worst teams/management (and by definition that is like...half the world!.)

For example, consider the concept of MVP (Minimal Viable Product). I once had a boss who kept re-defining the scope of the MVP until 18months in, we still had not completed the ever-expanding MVP. In light of these experiences, i'd rather follow methodologies to the letter just to avoid extreme abuse. For example, following some silly hard rule driven by methodology X that MVPs must be completed in 3mo would be helpful, even if arbitrary.
I think deterministic password managers are interesting solution for a small amount of secrets. But I don't think it scales out nicely.
Quickly glancing at my 1Password, I have over 200 saved logins. Some problems I see with your approach to a large amount of logins:

1) I don't always remember the username. In most cases it's my email address. But in some services I use a different email address. Some services (e.g Steam) do not allow you to change the original email address. Sometimes it's a username instead of an email. Sometimes the services will generate the username for you.

2) Password policies. Some of the websites have really ridiculous rules. What do you do when the format of the generated password doesn't fit the policy?

3) Services change names and domains - companies re-brand, sold or merged. Now it's another piece of history you need to retrace from memory ("were they called x-y.com or xy.net?") on first login.

4) Changing passwords is hard. If you share the counter across a group, bouncing it requires changing the passwords everywhere (or starting to remember different counters).
You never know when you'll need to change a password. It can be due to a security leak, or due to policy.

Not saying it cannot work of course, after all it works for you. But I don't feel it would work for me.
Tesla, the company that already got people killed?

Waymo has real world usage, both from self-driving cars which already use real streets, and from their worldwide street mapping fleet.

Besides, real world data is only as good as you can capture it, and Teslas are much more limited in that regard compared to Waymo's LIDAR.
It’s not about the internet. It’s about a government that’s fearful of losing its power. Feeling a need to suppress information means the government knows it’s doing something wrong, and it doesn’t want the people to know this. A government without a guilty conscience has no need to restrict the people in what information they can access about the government and its history. It’s a sign that something is wrong, and in no way is it limited to free internet access — internet censorship is just one symptom out of many.
The Little Thoughts of Thinking Machines – By John McCarthy (1983)
Not well known? Sure. GP didn't know about it, for example.

But "totally unused" is not an exaggeration, it is simply incorrect.

Thanks for the link. Interesting to read Interix founder and open source advocate's personal tales of interacting with early-2000s Microsoft after an acquisition that he didn't feel sufficiently compensated for. ;)
The key to cheap and non-harmful GNG is to have copious amounts of fats circulating, at a keto-typical low weight that means copious intakes of fats too. GNG ideally shouldn't/wouldn't happen from proteins (unless intake is very high) but from other metabolic byproducts and the glycerol backbones of triglycerides. Then this process typically accompanies ketosis in which ketones (endogenously produced-from-fat-burning types-of-carbohydrate but not from GNG) power most (not all) glucose-but-not-fat-burning-capable cells. Fat-adapted where possible, ketone-adapted elsewhere, and lots of byproducts that ordinarily would be "useless and to be excreted" (not just glycerol but also lactate, pyruvate etc) can now feed into (non-protein) GNG without the complications and expenses and downsides of protein-to-glucose GNG.
I've mentioned it before but I had a "aha" moment when I found intercooler js, it would be awesome to have 3-5 JavaScript functions instead of always rewriting and building Ajax request. Only problem with intercooler is it expects HTML in return instead of json.
> I wonder if tech would develop faster if there were a little less money involved?

Robotics is probably on the edge of this, between software (where it's probably true) and less-smart hardware (where it's probably false).

Having worked at a robotics lab, budget absolutely comes into play when you know what you need, but it's a custom part from a single vendor.
I don't believe job security code really works. If they're in a place where they're not paying any attention to you committing awful code why would they care when developers tell them that only you can work on your code?
Waymo does seem very disciplined.

However, on this:

"Waymo's car requires about an order of magnitude fewer interventions from safety drivers."

I'm a little skeptical about using interventions per x-distance as a metric for comparison.

There's just too many different things that could skew that. Like driving the same routes over and over. Or more/less stringent rules about when to trigger intervention. Or choosing when not to drive, like poor weather. Or purposely choosing difficult scenarios and edge cases for your routes.
Nice. I’m going to think about using ad hoc tags like this to tame my monolithic orgmode hierarchy.

Is there not an API in Evernote to query the notes? Seems like getting the last few weeks’ worth, sorting, and dumping to html or pdf would go pretty far for your diary use case.
Is America in a New Gilded Age?
It was dead for a number of years, but then revived again but now nothing for a couple of years.

One of the devs who was working on it has been improving qemus PPC emulation in the meantime though.
Mostly, yes, but Waymo has been testing in Kirkland, WA since February 2016.
I really think the two-semester approach works well. The first semester covers basics and intuition and tasks students to implement and extend. The second semester formalizes the material and tasks students to analyze and design algorithms to solve various problems. The first can be taught to first-years and the second to second- or third-years depending on when it's standard to take discrete maths.
Jorge Stolfi explains Bitcoin versus Bitcoin Cash versus Segwit2x
That's kind of what I meant. Spiral out to the right is kind another way of saying of bulges out to the right.
The worst thing about being a designer is that everyone can look at your work and think they have a clue even though they aren't experts. That's why I like low level programming. No project manager is going to look at your lockfree ringbuffer and tell you that it should be a few bytes larger.
The very very few cases where anything called a methodology works is when you deal with a repeating tasks: making a customized versions of standard tools, or what people call copy&paste development. SAP does it very well. Charges people 7 digits for "customized solution" that in reality is not customized beyond 20 lines of code from what the company sells to every sixth or seventh client.

The goal there would be to not to dive too deep into the task that is already solved in a way that "works well enough," and for what the client is already ready to pay money for.
I don't really understand what makes subsequent clip factories more expensive. In the first stage, yeah I understand why production units were getting more expensive. Some puny human was shortchanging me, that's why. That's why I enslaved them. But what in-game explanation is there for making the factories more and more expensive later?
I agree with you that a formalized methodology is required for you to start with agile, be it XP, Scrum, Kanban or whatever the flavor the team itself feels more comfortable doing.

What no one tells these teams is that the methodology/process itself should be flexible, should be allowed to change to accommodate the idiosyncrasies of their work environment. What I've noticed helping some small companies is that teams learn some framework and use that as their "agile" concept and then proceed to be overzealous of the process itself, completely forgetting the original manifesto.

Like always, it's a strange whisper game...
> Sometimes some developers feel that they should probably rewrite X or add Y and does so without consulting anyone first.

To be fair, project managers often decide to keep using X or leave out Y without consulting anyone first.

Also, to be fair, project managers are rarely organized or explicit about where the project is and where it should be with respect to cross pollination. If they tracked their goals there like they did other things, you'd see some developers taking this style of project under their wing.

That being said, my experience largely matches yours. Though I find the success rate in setting up a closed feedback loop (actually demoing for the actual people that should be happy with the actually deployed feature) is much lower than people notice, so I'm not sure agile is as technically useful as it seems. It's politically useful, for sure. You can say "Working on the wrong thing? I gave Henderson eight demos as work progressed this fall!"
That's how I felt when I attended my Scrum Master training. There was almost nobody in there who actually wrote code. The discussions were very abstract and about situations I had never encountered in work life.
Is it really that hard to compile it with a different icon?

There is probably a whole department on the payroll at Microsoft that decided this icon change after several long meetings. Just compile your own and let them do their thing.
Calamine: Excel file reader, written in Rust
The main problem people have with it is the resource usage

From what I've read on HN, people seem to generally like VS Code. (Replies to this comment by people who don't notwithstanding.) So is resource usage the main problem of people who use VS Code, or is it the main problem of people who don't like Electron?
Berkeley Lab Aims to Strengthen the Cybersecurity of the Grid
Soviets had clandestine beacons set up all over USA, and they also had an ability to home on civilian transmitters
Because it's mentioned in the article, credit where credit is due to Willow Labs for their incredible work in pushing the open source side of the field forward.

http://www.ros.org/about-ros/

Because of the nature of economics (vendors are either selling parts or complete systems), no one had incentive to work on a reusable OS / framework. This meant every lab project and product would start from scratch and rewrite the same stuff. From seeing this at a research lab ~2011, it absolutely impeded progress.

Grad students shouldn't have had to repeatedly reimplement all the utility bits just to test their ideas on a far more specific robotics problem.
I actually like the new icon :\
Yeah I know, I even downloaded an iOS app to read them ("Laundry Day"); but in practice I noticed most people just learn the one or two they care about and ignore the rest - because if you don't own a tumble dryer, you don't really care about the symbol for that. So if you care about Thunderbolt 2, you would look only for that icon, ignoring the rest; power might have a scaled one like washing temperature, and so on.

As usual though, the problem is that the industry has to come together to agree these symbols, be it formally through the USB consortium or informally in some other venue.
It appears that paper content is better than electronic, at least for retention of material:

https://www.theguardian.com/books/2014/aug/19/readers-absorb...

Ebooks also might negatively affect sleep:

http://www.bbc.com/news/health-30574260
Sublime 3 and VS Code icons have the same colors now, confuses me every time I am trying to run any of them from the dock.