skysight-inc/HackerNews huggingface dataset:
It's the approach in Brazil, and it does not work out. States heavily depend on the Federal Government and have to constantly plead for funds. It's a mess, and I guess taking into account the size the of the US, the higher number of states, and a huge difference in their wealth/GDP, the situation will likely repeat itself.
Building a callback system doesn't fix ss7 and is a bandaid slapped on top.
As a dev, "or solve it with microservices altogether" hahaha. Good one!
Other applications: https://www.acitydiscount.com/restaurant_equipment/search.cf... margarita machine
Because Elm is still a young language that hasn't found a solid footing that operates as a core philosophy, and usability issues and other concerns go unanswered or ignored for years at a time. When a language is very opinionated, and those opinions change, it creates a stability issue, and active releases and engagement with users help mitigate loss of confidence.
that sound is more of a eeehh or meeh depending on context. those two sounds verbally state "i disagree but dont feel like arguing"
Not only does Pittsburgh have dedicated bus lanes, they also have dedicated bus roads; roads where cars are not allowed to drive on (many are deprecated light rail lines)
Yes, it’s the little up arrow next to their username. It’s called an “upvote”. :P
Mu, a new Python IDE for beginners
The fact that this comment was flagged is deeply troubling to me.
Personally I find that the term tech debt gets overused. I've often heard it applied to relatively fresh projects for features/projects that just haven't been done yet, or to pitch the architecture of the day.

The times when I have seen a real breakdown where the term tech debt is legitimately used is when a scrum process breaks down deliverables below their smallest atom. E.g. different stories to write the code and unit tests, projects spread across devs such that no individual has ownership of any portion of the product etc.

In such situations we're not talking about debt as much as we're talking about junk.
Did reading the text help you any? Did the word "wiki" make sense in the context? (I suppose "lambda", "lisp", and "s-expression" are not very familiar to you?)

No snark here, I just try to understand how do different people read and understand a copy like this.
This is why people don’t respect lawyers.
tldr; - Think of Wikipedia. Even though it’s a web site with html, people who make edits do not create html. Instead they edit this nasty quasi-text document bearing a vague resemblance to markdown. This seems to be intended for a similar purpose in wikis.

post tldr - The terrible thing was this was painful to use and early on wikis had almost no structured data. So you have incredible amounts of useful information that mostly cannot be leveraged or processed efficiently because it’s a living nightmare to parse.

Over time things have improved. They added a wysiwyg editor so you don’t have to look at it. They’ve incrementally added ways to allow for documents and data to be more structured and parsable.

Not sure how far along everything is at present.
>I’d rather rewrite than understand

The people with this attitude seem to be the best sources of hard to understand legacy code.
I've been CTO (well, IT Director) for 3 years and I saw no particular problem with technical debt. I just handled it the same way I would handle financial debt. Repaying during good times and taking on debt in projects with high stakes and fixed deadlines.

It all depends on the industry as well. My CTO experience was in News and Media, where software is rewritten quite often and does not have any business value by itself.

I am now in a consulting position in the banking industry. Things are different there. None is willing to take on the risks associated with technical debt repayment. It accumulates endlessly. Once it reaches a point where no local developer would work on the project, the project is handed over to Asian sweatshops which support it indefinitely.
Ask HN: Do you have a side project you want to sell (2018)?
Haven't seen one of these in a while and I have money burning a hole in my pocket so it seems like an appropriate time to post a thread. Seems like one was posted a couple months back but no real responses so hoping this gets more traction
The RTP Summer Intern Experience Blog: Executives, Emails and the Electronic Rug
There are a few side-affects of technical debt that drive me nuts. These come from companies where developers are autonomous, self-choosing of time investment:

* continuous complaint without action (i.e. pretending to be a victim of the system you’ve built)

* lack of measurements for a system (technical debt or not, how is it working? Are you improving your measurement system after each failure to further understand the system?)

* unbuilt is better than unmaintained (this builds off the previous two — tell me what we learned from our previous attempts. If you didn’t understand the quality of the previous attempt, then how do we know if we actually improved?)

I’m down with fixing technical debt, just show me some metrics that prove that it was an improvement.
"modern transistors" are available in differently-sized packages. I assumed someone building their own CPU would be using larger transistors than those normally used inside a production CPU. You sure one of these[0] couldn't contain a tiny processor inside?

[0] https://images-na.ssl-images-amazon.com/images/I/41bBdtuYF0L...
Excellent!

Though that would have been an amusing test for a front end dev. "Can you actually troubleshoot a render issue to get the link in order to just apply?"
It's how it's done in Brazil and it does not work out. States constantly pleading for more money while the Federal Government wants to spend it itself, or gives preferential treatment to certain states, while others languish.
What YouTube could teach Facebook about conspiracies
The shiny is wearing off... But I agree, ideally, a tool isn't going to need a new version released every six weeks, if it is high quality and feature complete.

But expectations are completely upside down in the web development world, so that rather than things becoming mature and stable, they are seen as stale and abandoned.
Only SMM drivers run in the proverbial "ring -2". Ordinary UEFI apps run at the same privilege level as the host OS (0), just like any bootloader.
I think it is important to understand that technical debt is very difficult to define and quantify. Depending on your role, responsibility and skillset you will consider technical debt to be different things, and often attribute different (negative) impact of it.

Technical debt can cripple a development team, but I have also seen it being used as a continuous argument to invest into system development that really had zero positive business impact at the end. I am not saying to ignore it, but I also know that as a developer you tend to overvalue the things that are just in front of you.
I have no friends who are fascists and I've dropped people because they start espousing those ideas.

To me these are ideologies that go beyond just disagreement about how best to structure a society, how powerful government should be, or what its priorities should be. I think the thing they have in common is that they explicitly advocate hurting people and more importantly believe that you can actually make the world a better place by hurting certain people. You can make the world a better place by inflicting pain.

I think the defeat of Germany in WW2 has proved that's true.

So back to Thiel and his politics. Nowhere in his writing have I ever heard him explicitly advocate any of those things, but the company he keeps is another story. He seems to hang around with a fair number of explicit doctrinaire fascists.

explicit advocacy of genocide

Since this article's off the front page, it probably won't hurt to delve into politics for a bit here. So I have to ask: What specifically are you talking about?
I can't answer as a CTO-like person, but I'm in an Architect-type role and deal with our CTO-like person on a daily basis.

The high-level management cares only about "The Big Rewrite" because it is the only thing that gets visibility at that level of the organization and it comes with a large budget that everyone knows will be replenished for years as it gets spent. Our CTO-like person has fully bought into this idea.

We have too many projects and too few developers, so incurring technical debt is an everyday thing. It will be dealt with in "Phase 2" of the project, which all the developers know is something that never happens. From my vantage point - having one foot on the developer side and one foot on the management side, I see that the management thinks the developers are incompetent and the developers think the management is incompetent.

It's not a good position to be in, yet at the same time we have a pretty laid back culture, work less than 40 hours per week, great benefits, etc. So turnover is fairly low. Most of the developers have either a side gig or are going to school part time, or else they'd probably go insane.
Yeah I always laugh when there’s a project with no code written yet, but with plans for how we will “pay off the debt” that will inevitably be created.

It doesn’t need to be like that if you run your projects well.
> Zeus and Sherlock Holmes could both be argued to have had transitive causal influences upon us

There's some philosophers who'd argue that, but I think the arguments are pretty weak.
Mapping the Effects of California's Prop 13
There doesn't seem much evidence in the article or otherwise that Vietnam is quitting facebook. As it says facebook had 53 million users out of a population of 96 million. Also I've got about 40 Vietnamese facebook friends and have not noticed any quitting. It's pretty well known there that if you publish overthrow the government type stuff in any public media it's asking for problems and I don't think anyone thinks of facebook as a secure medium that no one can track you on. At least it's openly available as is the rest of the internet unlike China next door.

re

>"there is now no safe place left in Vietnam for people to speak freely,” said Clare Algar, Amnesty International’s director of global operations

You'd imagine if they want to post overthrow the government type stuff they'd use some anonymous service like reddit etc. Facebook isn't really the place.
The biggest problem is that Product and/or Sales are looking for constant growth via constant new features. It is impossible to get them to truly understand that by meeting some arbitrary deadline that you've had to take shortcuts. To their mind, done is done and now we need the next Y so they get their Q3 bonus.

The next problem is that too often the tech team wants to do a complete rewrite every 12 months because they want to use hindsight to remake last year's system/feature today. The issue is that in another 12 months this rewrite suffers from the same problem and now has several more things to consider. Some technical debt will always exist and I would argue always necessary. Perfect is the enemy of good enough and software that isn't live isn't adding value to the customers or company.

My perspective for this was to treat some percentage of work each quarter to resolving technical debt but do this in an agile prioritized way. Just like always focusing on the feature that will add the most value to the next release, also pick the biggest manageable issue that will reduce the debt the most to the next release. In this way, you know certain technical debt will never disappear but you have a ranked list to always decide the things that are most urgent and correct them before the house falls down. If your team is large enough, it is also helpful to have a person or standing task to update and document this list with WAG options and costs. Of course, as in all things, ymmv.
> They mention plentiful motivated job applications

I'd take anything from an advocacy article with a grain of salt.

> how is the market from the perspective of a developer looking to focus on Haskell?

Considering the only response you got points you to a subreddit, I'm guessing it isn't so great. At best, it is a niche market ( though that could be lucrative ).

I wouldn't put all my eggs in one basket. I'd make sure you have some expertise in Java, C#, C++, Python, etc ( don't forget SQL ) where there is a large established market that isn't going anywhere soon. But even more important, get experience in specific technologies ( databases , web servers, IDEs, version control, etc ).
No no, the prostitute did not perform any labour in this tale, she had already worked beforehand, but then on credit.
They have a lot of power, and plugging something like a thunderbolt device in can load an option ROM that runs there [1]. It is one of the reasons linuxboot is such an important project [2]. There is a great talk on why linuxboot is required [3].

[1] https://trmm.net/Thunderstrike
[2] https://www.linuxboot.org
[3] https://trmm.net/LinuxBoot_34c3
Figures in the Sky: How world cultures have seen their legends in the stars
Totally agree. And often if you make the effort to understand the code you can refactor it with reasonable effort to address the real problems.

A lot of rewrites I have seen just traded one set of problems with a different set of problems.
Pretty much. Once you’re negotiating with a DA, you’re going to jail. They’re never gonna let you go.
Show HN: Advanced search across 100+ image sites
He's not in possession of anything. He handed over everything he had to journalists in Hong Kong.
I'm one step below the CTO, but here's my perspective for what it is worth. It really depends on the stage of development your company is in. When you're first starting out, writing "good quality code" is about the worst thing you can invest in. The fact is, the code you're writing is almost certainly the wrong thing. A new startup is a hypothesis on a business model, and the first bit of code is to make the most basic tests of the hypothesis. It's VERY rare you get it right your first try. Writing good quality code is a long term investment, but if there's no one willing to buy it, it's a bad investment that will never have an ROI. On the other hand, if you're rewriting the system because now you know the market, and you know what it wants and you're scaling to meet it, now tech debt is bad. I think it's critical to understand the first system can and probably will be thrown away, so it makes little sense to build it to "scale".
Well, Mugabe was a Marxist. Gaddafi's government was the "Great Socialist People's Libyan Arab Jamahiriya". I don't know if Assad has any ideology, but his party is the Arab Socialist Ba'ath Party, and he has been supported by Venezuelan and Nicaraguan dictators, Algeria's National Liberation Front, South Africa's ANC, etc.
"The point in contention isn't that infinities can be imagined, it is whether they are useful - specifically in the context of cosmology."

Going the other way may be more useful; is it possible to create a correct model of reality that does not at any point use infinities? You could have alternate correct models that do, but if you can create one without them you'd have a reasonable basis to call the infinities in the other models unnecessary and nonexistent.

(I would suggest before anyone rush to correct me that they read what I said carefully. For instance, "reasonable basis" != "undeniable proof", which experience leads me to believe is a difference a hypothetical replier might, in their rush to reply, overlook. Also note the two clauses in the question; if it is simply impossible to create a correct model of reality at all, we may never get to the "infinity" portion of the question.)
Oil is not too far from the all time highs, it's certainly much higher than when Chavez took over. Why isn't everything better? They killed basic market economics, including (especially) in the oil industry. They made it so people are afraid to invest in business in Venezuela. They didn't want to admit that their policies were killing the economy, so they doubled down which just made it worse.
I try to use an economic model for all software. All code is a loan against taken against entropy (a liability).

Best solution is no code or a simplification of the problem to existing solutions. This results in zero liability, while the revenue the solution generates is pure assets.

When a code liability does need to be incurred, consider both the amount of code written (the principal of the loan) and the architecture of the solution (the rate of compound interest). A good programmer will work to reduce the principal, an excellent one will work to reduce the rate of compound interest with a simpler architecture.

The architecture that is does more by adding complexity and conditionals / code contains a horribly high rate of compound interest, even if it seems easier to do at first.

Architectures which do more / everything by virtue of being simple may be more difficult to implement and understand (especially without some background knowledge) but can have a vanishingly small rate of interest. Double entry bookkeeping, graph theory, pipelines, normalisation/denormalization, map/reduce, unidirectional data flow etc.

For any serious business investment (not an experiment or proof of concept), architecture as rate of interest always trumps quantity of code as principal.

Order of priority is
1. Don’t take loans
2. If you must, design until you have a low and manageable rate of interest. Revisit often.
3. Reduce amount of code.
I have met the Queen of England exactly zero times.
I’m confused by the discussion of bringing new programmers on a team up to speed with these lesser-used languages; this blog is quite explicitly from a one-man dev shop.
Hackers Breached Virginia Bank Twice in Eight Months, Stole $2.4M
I'm making the argument in the opposite direction. Communism and socialism end up as dictatorships, when not already bootstrapped as one.
Clearing the TensorFlow to FPGA Path
Shallower DoF, yes, if you need something razor thin like 1.4 or 2.8 zooms are sharp enough for you.

Higher Resolution, yes if you need 50mp because 24mp is not enough to print 3m x 2m.
Wix vs. Squarespace: A comparison for front end developers
On my my mobile device I get some imagery (a face and a building) and text all stacked on top of each other, making the text very hard to read.

It would be good to have a single clear statement describing the aim and purpose (what and why) of lambda speech, followed by a description of how to use it. Otherwise people will give up in confusion
it would be great if there was a way to crowdsource telescopes and I could throw something on my roof or out my window that could somehow be part of a global network to watch things and making findings as a community.

I dream of a day when research is paramount and our government budgets reflect that to further science for the sake of science

If I win the lottery I want to hook a mini-observatory to my tv in my house and look around space through my tv with some sort of custom controller.
The complete wavefunction of you and the Queen of England involves a handshake-like fluctuation in the distant decimal places.
Free Content for Website and How It Improves Business
> "you're too close to the bus in front, wait a bit at the next stop"

That's one way to infuriate the passengers on the waiting bus.
On mobile I see no reference to any of those words or help. I also have no idea what's going on.
Quick temperature changes. Bright light. Weather changes. Wearing something tight-fitting on the head. Large changes in stress level. Caffeine withdrawal is a big one. Getting 10 hours of sleep (first night) then 5-6 hours of sleep (second night) is a common cause for me.

I think the #1 underlying cause for me has been not getting enough hydration (or having electrolyte imbalances), though. As I've upped my daily fluid intake, they are occurring less often in general.

Though, it's changed over time. At one point my most common trigger was stress. Since I've changed jobs, that also has helped reduce the frequency, very noticeably (was getting multiple a week at a stressful/hated job)

It's odd because different days, different pain meds seem to work better. Aleve/Naproxen has the best overall efficacy for me, though. That, and/or putting something cold on my face and neck and being in a darker room.
Not sure where you're reading this. All I can see is this page http://b2b3.free.fr/lambdaspeech/?view=start
I've been the CTO at two tech startups. Here's how I think about it.

"Debt" is a good metaphor because by accumulating it, you get advantages right now in speed and ability to focus on other things, in exchange for having to pay it off later. You can either pay it off by stopping what you're doing (uncommon) and fixing stuff, or you can do lifetime installment payments of more complexity, bugs, etc.

Tech debt is just one aspect a CTO has to manage. Time to market is pretty damn important. Features are important. Many other things too. This is not to say that tech debt should be ignored, but elegance of the system is not the paramount concern. Just as startups borrow money and take financing to move quickly, so too a responsible amount of tech debt can be a good thing.

In engineering we tend to over-emphasize how important the technical qualities of the system are because that's what we see every day. There are a great many things that are also important, and various business scenarios where they become MORE important than tech debt. But if you're in the stage of trying to find product-market fit, you probably have bigger fish to fry.

The biggest tech debt I've struggled with always comes from the same patterned source. You think a system is intended to have a certain feature set for a certain user base, and so you make a set of architectural decisions to match. The world moves on quickly, you adapt, pivot, whatever you want to call it, and suddenly your carefully made architectural decisions are no longer correct or wise for your new scenario, but there is no time to go back and have a "do-over".

So in essence, failure to be able to tell the future, paired with a constant need to move forward, is the source of the problem. Both of those things are going to keep happening to startups forever.
Yes that's a good starting point. And a great option if you have the money for it. This will also support the people that put in hard work to achieve and provide ultimate user freedom.

If you are on a tight budget however i recommend buying the motherboard on aliexpress (for about $200) and if you are not comfortable in flashing libreboot yourself you can ask a company that delivers bios chips for this motherboard to flash a custom bios and supply the libreboot rom binary to them. You can easily swap the bios chips yourself. The libreboot and coreboot websites have lists of hardware that are compatible (ram/cpu).

Also if you are interested in newer liberated hardware, look into the Talos II. They provide a proper workstation that comes with only free software. It will be more difficult to setup since it has a different cpu architecture, but it is definitely the way forward.
“Eeeh” or “meh” would indeed signal mild disagreement, but it’s stronger.

I’d say there is a slight inflection to the “uh-huh”/“sure” (almost a low-tone questinging iflextion?) to indicate less-than-full-throated-agreement, but that’s difficult to convey in writing.
The := is missing! No wonder Guido would leave its BDFL position!
Venezuela, one of the world’s oil rich nations got the back hand of the resource curse. It pains me to see how much their citizens suffer.

US and EU have their problems and aren’t perfect, but makes me appreciate how far we’ve come as a functional civilization.
Why are they not using ghcjs? Wouldn't that work nicely with their existing infrastucture and codebase?
Apple is not part of FANG. It is an acronym coined by Jim Cramer for companies that have hyper growth.