skysight-inc/HackerNews huggingface dataset:
This is malware and should have been rejected from the App Store months (if not years ago). Better late than never.

I'm sure if it was a smaller company doing a similar thing they wouldn't have been given such leeway as Facebook was for so long.
Look at platforms like Udemy (selling online courses).

They take 50% of your revenue and not only that, they also control the prices of your course by selling them for $10 year round (of which you'll get $5 for a ~5-10 hour video course that takes 4 months to make and it's also expected you offer 24/7/365 support).

Yes I know you can opt out of these things but then you're hidden from search results by default which defeats the entire purpose of using a marketplace.

As a content creator I despise marketplaces because you lose control over your business. You don't even get to contact your customers directly since details like emails are hidden from you and you either make or it fail based on their search engine's ranking algorithm.

As a content consumer, marketplaces make it pretty easy to find good things, but at the same time I feel like if you have good content, people would find you without a marketplace.

I can't wait until these marketplaces eventually bust from content creators just picking up and selling stuff on their own.
It's not moving further away. It's increasing your catchment area. It's reaching down into the pool, to people who didn't go to the right school, or have the right connections, who still never the less show promise and aptitude and say "You. Come with me. We're going to do cool things."
Why do you think they're the only one, don't you think maybe they enjoyed a very special set of circumstances that will, more than likely, never happen again?
Here are a couple of images I was given by an Aerospace Engineer recently. I don't know if he was trolling me or not, so I provide them without further comment.

https://imgur.com/a/GoEzEdl

https://imgur.com/a/zZS3nti
It's the same for restaurants in low-volume areas. That under-4-star death knell is a killer for sales.

On the other hand, I love perusing those 3-star restaurants as I find so many hidden gems covered in the tears of LLC owners and bored hostesses.

If I were a lesser man, I totally am, I would write a book concerning that social theory called the Star Divide.
Maybe people are over critical but the service and experience of a meal is not to be ignored. I'm sure you would agree that if they literally threw the food at you it wouldn't deserve a rating regardless of the food.
The title does not match the headline on the website. The headline should better reflect the headline: "H-1B visa-reliant Cisco ‘secured visas for foreign workers instead of hiring U.S. citizens’: report"

Otherwise, it seems obvious that US citizens would not need visas.
Im not 100% sure its all of them (malls and airports come to mind) but yes its a vast majority.

True I didn't consider the cable investment either. Normally the landlord pays for this but I imagine chickfila probably pays for part of the bill. That I dont know though
Comparing distribution of physical goods is a poor analogy as the variable costs are high, and low or zero for App Store developers. We know from tariffs that a 30% fee on mining or manufacturing increases costs and reduces trade, but despite Apple’s 30%, the cost of an app has been driven down. This suggests that a high revenue share of a software sale is viable in a way that a high revenue share of a truck load is not.
People apply the word 'fact' loosely when it comes to topics they feel strongly about. The point is contentious and disputable in a bunch of ways. That's not necessarily bad, but it is when combined with a declamatory style. Just to be clear though: I'm not making a point about China. I'm making a point about how terrible Hacker News threads become when people allow themselves to post this way.

This problem is getting worse as nationalistic feelings are heating up all over. If we're going to keep HN alive as a place for thoughtful discussion, we need users to control their rhetorical impulses and consciously respect opposing points of view. HN is a large for a single internet community (5M readers a month), highly international, and replete with opposing points of view. That ought to be a good thing if we don't tear ourselves apart with them.
But can’t AWS pay RedisLabs for those modules? That’s exactly what RL are after - a cut from the big hosting providers. If the demand is there (for the modules) then you’ll be able to license them via AWS.
Well it is definitely blocked last time when I was in China, or in Beijing, but that is like 3 years ago.
Why should only the food matter?

If I have to wait one hour to get the food, that is detrimental to the experience in my opinion
I'm interested in this issue in the realm of gaming.

The way I see it Apple and Google tax mobile games for using Apple and Android phones as gaming consoles. How does Nintendo, Sony, and Microsoft(Xbox) handle revenue share and developer licenses?
Popularize the value of tests. Test, refactor, repeat. 2 years of legacy spaghetti isn't really that bad. I work for a company whose codebase is at least 14 years old in places, and there have only been serious testing efforts for 2-3 years.

Chances are, the code is a mess because nobody who knew better was empowered or motivated to advocate for a better way, but you have a hidden opportunity to be that hero.

Good luck!
Intel and ByteDance Partner on AI Lab
I interviewed there in 2016 and you only needed to have the app on while driving for a week or two before you got a quote. After you got the quote you didn't need to have the app on. It's possible this has changed since then; but back when I spoke with them they were clearly trying to balance collecting the telemetry needed to give good discounts with the natural privacy concerns.
> I've already made some comments about rewriting it and the response was basically "ok".

Do it.

Gradually.

Rename. Simplify. Reduce. Enhance. Test. Slice and dice.

Embrace the shitiness. Accept it. Own it.

It's your playground. Sharpen your skills, and lead them to the promised land.

It could be worse. You could face major resistance and people issues. Appreciate it.

This is an opportunity for you to kick a billion miles of ass...
> a single individual could need multiple sequences stored.

And multiple sequences could be hundreds, thousands, or more. Example: single-cell RNAseq pipelines that generate sequences for 10k cells at once.

Perhaps in the future--as tech improves--the devices themselves might be equipped to run more real-time in memory QC and emit less--but more accurate--data? I believe this is somewhat how CERN does it, where they only record a filtered subset of the data that comes in.
Email me, I’m in a very similar situation. Let’s chat.
IBM Supporting the Java Community
Ok, lets go thru that list:

- Credit-card transactions don't have low-latency requirements, its 'nice' if they're quick, same as everything else. The bottleneck here is entirely dependent on your ISP tho. No 'edge-computing' here.

- Mobile orders. This will necessarily go thru to a central server. This is traditional client-server stuff. Again, no 'edge-compute'.

- Order receiving. Simple local data entry. Again, no 'edge-compute'.

- IoT devices. Hopefully these have local control systems without the server being in the loop. Control systems are not 'edge-compute' either.

'Edge-compute' is generation of knowledge at the edge rather than shipping raw data to a central server. This reduces required bandwidth.

What in your system takes a high rate of data and generates a low-rate of data for transfer to a server for further use. I see no analysis of raw data into a more processed form, this is simply traditional data entry and CRUD activites.
Somebody fathered a legacy codebase.
> To be fair most of the complains were about the model.

To be fair, if they'd just said hey we're selling these proprietary licensed modules then there wouldn't be much of debate. As others have pointed out, many other OSS projects do just that.

Instead mass confusion has erupted and literally every word debated ad nauseam -- including, now, the model.
There's nothing wrong with open source as long as you are honest to yourself regarding the intentions.

If you go into open source expecting to get paid, then you're gonna have a bad time.

If you go into open source for the accolades, then you're gonna have a bad time.

If you go into open source with a true desire to improve the state of the art, then you might be able to succeed.

We (https://sheetjs.com, our most popular library https://github.com/SheetJS/js-xlsx has over 11K GitHub stars) combat that by intentionally removing our names and egos from the equation. We are happy to see others use our open source code in their applications, and are constantly surprised when high-profile projects like React end up using our code (https://github.com/facebook/react/blob/v16.0.0/src/renderers...). Our intentions are clear: the open source offerings give us a test surface far larger than any proprietary solution, and for that we are extremely satisfied with the results.
3 thoughts
Maybe, but I think it is safe to assume that the ISP backbone is not the bottleneck.
All the issues the author talks about are valid, however, the idea that no one warns you about them is wrong.

If you do even the most basic research into Event Sourcing you will find people warning of these trade offs (foremost amongst them Greg Young, the person who originally set out the idea)
> how am I doing compared to previously/expectations/other people?

This is a twisted way to view happiness. Wouldn't you be happier if you helped others succeed? Feel connected, part of something you really believe in?

Happiness is so much more than prosperity. Money helps you avoid death. Happiness exists on an entirely different foundation.
I guess "one way to do the thing" motto is at work here - run python as modules every time. I guess the script part should run the file it contains as a module for graceful fallback
I hope the Apache Foundation speaks out against this horrible potential for confusion. Could this possibly be turning into a case of trademark dilution (of the "Apache" trademark)?
>It may or may not reflect on the original developer. Maybe they were learning a new framework. Maybe they were rushed. Maybe it was originally intended as a prototype but ended up in production. Maybe the requirements have grown or changed significantly since it was implemented and the original design didn’t scale well

Well said. There are many possible causes behind a poor codebase, and it's rarely useful (and almost never persuasive) to go into finger-pointing mode. The issue for the OP is: from the business's perspective, is the poor code a problem? If it's not, can they live with continuing to work on this code in this job? And if it is: what's the next step, and what can they contribute to making it happen?
Affirmative action but for VC? Are the A16Z partners so incorrigibly racist that they can't, you know, fund African-American founders themselves?

> all of the fees and carry associated with the fund will be donated to non-profit organizations that enable African Americans to enter the technology industry.

A16Z is ostensibly a for-profit business: by donating all the proceeds from this fund, they're basically saying outright that they expect this to be a small peanuts social outreach job, and have 0 expectation that this will turn into a viable long-term fund.
That's a bit much. It's unlikely that even if she was a citizen they would have disappeared or killed her. More like give her a firm warning and lecture and a vague threat or two of what may be to come if she keeps it up.
EvE doesnt really require micromanagement its all macro based mostly(possibly, alot of it), so multitasking is realistic with EvE.

Alot of real money goes through EvE, sometimes in the hundred thousand dollar range

https://www.google.com/url?sa=t&source=web&rct=j&url=https:/...
Before going to management to talk about someone, I would talk with that person. Maybe he/she hates the code as much as you do. Sometimes, shitty code just happens. Avoiding it is part of the job, but not always a possibility.

And if you have the option to rewrite it and you think you can do a good job, go for it and good luck!
You are absolutely right. I grew up on Vancouver Island. And the giant Sitka Spruce is a coastal tree.

See https://en.wikipedia.org/wiki/Picea_sitchensis for more, including a map of its range.
Let's Make Masonite Framework and Laravel Mix Work Together
Simple file I/O is such a great task to blog about as there's a long evolution of 'discovery' permitted:

1. oh wow, syscalls are really slow. We need to get as much done as we can with as few of these as possible

2. that's kind of annoying though, what if we had ... some kind of ... transparently buffered ... interface?

3. woah that buffered I/O thing I discovered last time, I just found out that my C programs have been using that this whole time! what cheaters!

4. hmm, even though I have 9000 CPUs each trying to process I/O from this single filesystem, I'm not getting the 9000x speedup I would expect. wait, wait. I just had a thought. try and keep up with me here. Filesystems must exist somewhere in reality, right? On some part of my macbook? What part is that?

5. oh wow spinning disks have really weird performance characteristics

6. oh wow it's enormously faster to read serial data even in RAM! Even though it has 'random-access' right in the name, random access is slower! This is going to be an epic-length blog series guys! We're rediscovering everything!
No they’re not, because it’s increasingly expected of developers to have a track record of open-source contributions if they want to move up into the higher tiers of their profession. That amplifies inequalities in the field between:

1) the top 1% employees in the field who have the luxury to invest unpaid time, and the social clout to make their projects more successful, or to join more successful projects. (example: how much more likely are you to be a key contributor to Kubernetes if you are, or were at some point, employed by Google?);

2) the other 99% who cannot afford to invest the spare time, and do not benefit from the social proximity to successful open-source contributors (and success in open-source is as much about social proximity today than technical skills, hopefully we can change that in the future);

3) The corporations who benefit financially from open-source, sometimes enormously, with very little pressure to contribute back because of the aforementioned social pressure on individuals to contribute on their free time. The expectations are so low that even modest corporate contributions (joining or starting a foundation, hiring a few engineers, paying for a conference) will be hailed as generous and benevolent, because the bar is so incredibly low.
The point is that the definition posted is narrow and bad. This isn't some obscure technical point, a debate about the proper usage of 'less' and 'fewer' or whether 'literally' literally means what it says in some odd case. All you have to do to convince yourself of its badness is read a newspaper or magazine or listen to a news report. What exactly would 'racial bigotry' mean if the posted thing was the only definition of 'bigotry'?

As to pedantry, you're the one who started arguing this clearly lousy definition is not lousy, brought up the OED, decided the OED is no good, finally acknowledged the existence of a broader definition but then somehow decided that it's, in fact, as good as identical to the narrow bad definition. I'll be the first to acknowledge I have a habit of getting involved in some deeply silly threads but I'm left utterly flummoxed by this Cirque-du Soleil-level display of mental gymnastics.

I just hope the authors of that lousy definition aren't holding your cat hostage.
I always found the commercial open source community to be a bit too idealistic. On one end you have developers from very wealthy companies driving these hyped up projects.

Sometimes those same developers will leave that wealthy company to start the commercial vehicle for that project. They talk about the wonders of open source and free software.

Obviously their next move is to monetize the project with commercial add-ons and they end up charging 6 to 8 figure price tags for 'free' software. Their enterprise customers justify this by saying 'we have the source code for the core product...its open source so we won't get locked in'. But the likely hood that some overgrown Fortune 2000 IT team will use the forked source code and not the shipped enterprise product is basically zero.

At that point, the FOSS nature is just a farce. It might as well be proprietary software at that point. There's no way the same company will prioritize the community over the high paying customers. They take over the development of the core open source version. They end up hiring all the main contributors. They find new ways to monetize it. They build add-ons that are end up being essential to using the same project in production. Its no longer a community-driven engineering meritocracy, but simply an enterprise development team with a github page.
is improving old code really what you want your career to become? this is a selfish question, but you need to put your own needs before that of the company. you are not a charity. they are selfish. be selfish.
There is no real edge-compute loads here, just traditional CRUD data entry type systems.

Riding the hype-wave methinks....
Please, please direct me to such a housing market. I am desperate to find such a home.
One thing you can try doing is to rework sections of the codebase gradually over time as you change them. Don't touch code that is working and doesn't need to be updated, but if you are working on a feature in one corner of the codebase, see what you can do to improve that part of the codebase.

This is easier to deal with both in terms of selling it to management and making sure you don't actually break the whole system compared to a full scale rewrite. I've made that mistake before and it wasn't fun. As others have said, code that's in production and works and is making money has value. The "cleanness of the code" is not something business owners care about, unless it causes problems.
That's true.

When the concept of open source software was first introduced, it was seen as a desperate way to get users but it was an effective strategy at the time.

Today, giving software for free is not enough - I think that the next trend will be to pay people to use your OSS software. Probably with cryptocurrency.
Sure, I agree that consumers use video games, for example, for personal enjoyment, whereas cloud providers use OSS to make millions.

But that difference does not change the market dynamics in any way. In both cases, the effects of a near unlimited supply of creators is having the same effect, regardless of how their creations get used.

Perhaps the difference changes the ethics of the situation, I don't know, but I remain equally skeptical of "business innovations" being able to help the OSS creators as I am "business innovations" being able to help aspiring rock stars and shortstops.
This seems like such an over-engineered solution.

It would've been much simpler to have a plate with multiple pressure sensors and a multi-color LED per spot. When you set the fries down on the sensor it activates and the LED turns green. After X amount of time the LED can turn yellow, meaning that it's becoming stale. Finally, after X+N time has passed and it's no longer fresh it can turn red. Removing the fries turns it off. Aside from being way cheaper, I'd conjecture that this would be much more reliable. I'm pretty sure I could get a prototype of this up and running over the course of a weekend or two.

If you wanted to get really fancy I guess you could also track the room temperature and moisture levels and use that to get a better guess of how long a group of fries will remain fresh. Although I don't know if environmental factors like these have enough impact on fry freshness to be worth taking into consideration.

Anyway, it looks like they were just doing this for fun and learning, so I guess it doesn't really matter.
No, it's not good news. At best, it's clueless. At worst, it's propaganda. Trees are not interchangeable objects to count. What matters is not trees, but ecosystems.
"Error 1001 DNS resolution error

What happened?
You've requested a page on a website (archive.is) that is on the Cloudflare network. Cloudflare is currently unable to resolve your requested domain (archive.is)."

Domain blocked?
Also helps never to mix company and private email (separate email accounts) and code (two computers). If the side-project becomes any serious, e.g. you want to register a trademark or you have to change your tax status because it brings in extra money, try to get approval in writing, can be as simple as an email.

If the company tries to claim "yes, it' in the contract, but we don't enforce it" you could point to the Facebook movie (The Social Network), where lack of clarity/paper-trail has cost somebody 10s of millions.
"The earth is flat (p > 0.05): significance thresholds and the crisis of unreplicable research"

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5502092/
There's a book called "Working Effectively with Legacy Code" by Michael C. Feathers which I heartily recommend.

I got it a while back when working on a similar sounding codebase and it was very useful. It's got chapter headings like "My Application Has No Structure" and "I'm Changing the Same Code All Over the Place".

If your company has a books budget get them to buy it, but I'd personally drop the £35 it costs on amazon given how useful this has been to me over the years.
An Update on Our App Investigation
Flowery is not what we're looking for. Thoughtful would be more like it.
Sort of. It is probably better but if you don't have stable living conditions, which many people don't, that affects everything else. So you can say that people have access to daycare, but if you involuntarily have to move around a lot that is a real overall decrease in quality of that daycare.
This sounds normal.

Back in the 90's and early 2000's, almost nothing had automated tests. Miraculously, things still got done by manually testing.

On the other hand, I worked at shops where every getter and setter had a test. Not much got done there.
If you’re going to take this to management, I would not bad-mouth the original developer.

This. If there are deficiencies in the code base, focus on those, their effects, and the gains from fixing them. Blaming people is rarely a good idea, for many reasons.

If the original dev worked on the code base for a long time, they're probably already aware of them. God knows I'm all too aware of the deficiencies in code I wrote years ago, but that's frequently how things look after years of updates and feature creep. Everyone on our team has code like that, and when new guys come in and point them out, we just sigh and say "yeah it would be great to rewrite that knowing what we know today". But budgeting time for that is not easy.

Edit: Also, like others said, I think you need to adjust your expectations. Working with code like that is life, and you should appreciate the fact that you, with your outside perspective and youthful energy can make a change for the better. But it's going to involve lots of refactoring and test writing.

The "Legacy Code" book referenced in another post is a great overview of this. I'd say of all programming books I've read, it's one of the ones that are most relevant to my day to day work.
This makes me wonder, if redhat started in this cloud poly era, would it even be possible for them to succeed.
Not to mention the fact that total world population has likely increased even more than the number of trees. (No idea though, would love to see the numbers)
Of the Linux kernel was under AGPL, they would probably just use some other code under less restrictive license instead.
Yes, so good. Martin Fowler's Refactoring is an excellent companion to Feathers' book.