skysight-inc/HackerNews huggingface dataset:
Nico I ha estado major issues and they were the original reason for switching from Windows. I'd love you feedback on them.

1. Apple doesn't slow down due to not being rebooted. I rarely reboot for this reason; basically only for system updates.

2. Suspend I believe is the service? I just close the lid, open, login and keep working. This last time I used Windows wasn't possible. From crashing applications and the direct loss of data due to that crash to not waking and needing me to reboot the whole system.

3. My entire experience with Windows aside from the need to frequently reboot is that it always slows down from the first day of purchase until the day I lose my mind over the speed of it's activity and go buy a new one... This slow down is the slower more incideous one that progresses over months until nothing not even a reboot nurses enough out of it to make it performant anymore.

These are literally the three issues that cause me to be terrified of switching. When Apple did the 'it just works' commercials I switched, because I didn't want to be so involved in the OS. I wanted to just use it and do my things, which aren't nearly as intensive as some others ex. I just do front end work minus the crazy designer apps that require huge RAM and expensive Graphics Cards.

If these 3 things are no longer issues on Windows then I'd really consider it because they are the only reason I'm with Apple at this time. Since Jobs died they've gotten even worse at servicing their MacOS base that it's crazy to be using their product at this point, since they clearly don't give a shit about us.

Lastly I used to use Linux back in the day, but left it because the lips stick (GUI) doesn't abstract away enough of the day to day tasks and I refuse to be a 'programmer' when I just doing regular stuff like writing emails, productivity tools and looking at photos. I'd totally be game if losing a file on download wasn't still a distinct possibility along with the anxiety of not knowing if an app was installed right or full removed; an issue I have with Windows too btw, but not with MacOS.
As someone who has lived more than an extra 10 years of life due to receiving a transplant, I am very happy to take my daily immunosuppressant medication.

For context, I was in my 30s when I had the transplant. If I was 70+, then perhaps I might pass.

I hope you are never in the position of being on a waiting list for an organ donation, but it is much easier to dismiss an abstract idea of saving some unspecified life versus facing short term uncertainty about your own continued life.
I have no idea how this addresses my question asking GP to clarify its misconception.
Pytorch has the best API to understand deep learning and Pytorch based Pyro is also very good for probabilistic programming (fresh take coming from Stan/PyMC3)
I used to avoid the DevOps title and called myself just straight Operations. But recently, and I mean within the last week or two, I realized I'm squarely in DevOps territory.

The system I Op runs really smoothly. Problems are infrequent. So instead of spending my time fighting fires, I'm instead working on our next generation infrastructure, running experiments with Kubernetes and Kafka and Influxdb and Elasticsearch.

I'm not developing on our main product most of the time. But I am developing our infrastructure.

As far as the totem pole with developers at the top, able to do all the other jobs? That has not been my experience. In 30 years, working with probably 100+ companies large and small (for 18 years I did contract SysAdmin), I'd say that the developer who even thinks about ops is extremely rare, less than 10%.

I agree that DevOps is more important for smaller companies, and that specialization is useful. I haven't seen evidence that supports the totem pole portion of that post.
But both the Bit and the Pi fall between two stools.

8-bit micros like the Spectrum and BBC were powerful enough to get useful work done, but simple enough to offer simple instant gratification.

You could learn everything you needed about BASIC from a fairly small paper manual, and after that - or sometimes during - you learned the rest by example from monthly magazines.

The monthly format worked very well, providing a digestible amount of information on a regular schedule.

The Pi is a complete different experience. Command-line Linux is completely unsuited to most beginners, and desktop Linux really needs command-line skills to be usable. The Pi tries to teach Linux, basic electronics, Python (etc), and simple web tech all at the same time, and that's too much ground to cover at once.

Meanwhile the Bit is too simple to be useful. You can make LEDs flash on and off, but that's not nearly as exciting as being able to write and play a complete game.

I'm occasionally surprised no one has built an 8-bit-like neo-micro booting into the Python interpreter, which is probably the closest thing to BASIC we have today.

Although given that everyone has a phone now, and most people have tablets and desktops, the ideal modern environment would probably be something like a more accessible version of Swift playgrounds - if only because that "You too can access incredible technology at home" thing is an historic relic now.
i know of a company that has defined a position where a single person designs and sets up some technical equipment for two totally different departments led by two different, competing bosses.

this job-holder is routinely overworked and faces extreme demands on their time, requiring on-site presence both early in the morning and late at night. the job-holder must mediate interdepartmental conflict (two bosses). and there's no path to promotion.

the company keeps losing people in this position. it keeps casting a wider net, bringing in people from further and further away.

this is a solid, successful company with a reputation as one of the very best places to work in the county. but it has never bothered to redefine the position into two or more separate jobs. it's just churn and burn.

i'm not sure what the moral is. managers exploit the labor pool until they can't any more. then they look for another labor pool. if that doesn't work they whine and complain that they "can't find workers" to fill their jobs.
>done wrong

Let me pose a rhetorical question: Why have all the hot trends in software project process/management for the last 10 years been so risk-prone to being "done wrong"?
That so bad about AGPL, that require a fork?
Good for you for taking the lead.

As someone who has had DBA in my job title before, it saddens me to think DBA was needed to explain the importance of foreign keys or indexes (this should be general developer knowledge at this point). As a general rule, any field used in a join or where clause is an index candidate. And foreign keys (along with other constraints) are like type checking in code. They help you not do anything stupid later.
Haters gonna hate, I guess.
My thoughts on full-stack is like your thought. It's a developer position. Once you start throwing in tasks that include the word "administration" in the description then that's likely a different job for a different person.
> the State of North Carolina actually gave me free tuition and paid me a stipend to get my Master's degree (free/cheap government education is a benefit which you don't have to be privileged to get, at least not as privileged).

If having your advanced education paid for doesn't make you "privileged" you might as well stop using the word since it no longer has any meaning. I mean, seriously.
These sequential models are are like Fibonacci function comparisons between programming languages.

They are simple and basic, difference between 5 lines of code or 20 lines of code makes no difference. You spend very little time actually coding these layers. Understanding the model, default parameters used underneath is more important.

It would be nice to see some examples with skip-layers, weight sharing etc. You you have to drop sequential model to do them or not?
Founder Interview: Smart Startup Growth Starts Early
Monitoring 9600 banks at scale
You shouldn’t need a DBA for a small or medium project. Any developer who hasn’t taken the time to learn basic RDMS theory like normalization, indexing, foreign keys, etc. doesn’t take thier craft seriously. Knowing the basics of how databases work is a required skill in almost any implementation.

The issue is “framework developers”. I am not opposed to learning and using frameworks but you should always know at least one level below the framework you are using.

If you are a web developer who uses Angular/React and Bootstrap everyday you should know JavaScript, CSS, and HTML well.

If you use an ORM, you should know enough about how databases work to have a mental model of what the database is doing.
TLDR; Apple and Samsung seem to be tired of fighting this fight, so they settled. They have each spent hundreds of millions in legal fees on the ordeal and they avoid spending hundreds of millions more by settling the ordeal, which can go on a long time.
May I ask what distro you're running? I tried Ubuntu 16.04LTS some time ago, and it didn't seem to get along very well with my mid-2015 MBP.
lately I discovered that many developers don't know SQL and didn't attend to any DB course at university

My DB course taught us relational algebra and calculus and you were expected to learn SQL independently.

I am constantly bemused tho’ at the extraordinary lengths some devs will go to to avoid SQL. I’ve known people who will grudgingly do SELECT * FROM table; then extract the one row/column they want on the client. Then they complain that the DB is slow when it’s loadavg is 0.01...
I've heard it called Cache Stampede. Any decent framework for memoizing method calls would cover this case though.
I hope somebody makes an Eclipse plugin out of this, and integrates it into the TeXlipse LaTeX IDE. It is a sad state of affairs that this aging project (last release was in 2011) is still the most versatile TeX editing environment. For example, it is the only one that I am aware of, beyond command-line editors, that that lets you open up an arbitrary number of views of the same file, which is often needed in large TeX projects. Its current PDF viewer (Pdf4Eclipse) is broken on Hi-DPI displays.
Isn't Flask simpler for REST stuff?
Docker Swarm - you have 80% of the power of kubernetes and 10x simpler.
Different technology. PyPy/RPython is a more "high level" approach built on top of metatracing while OMR is more low level and geared towards method-at-a-time JIT. (I might be wrong. I worked more with pypy but only know OMR superficially)
Annie Leonard has a great piece on the history of the "individual accountability" trash movement. TL;DR: it's an accountability avoidance maneuver by the drinks, beverages, and fast-food industries, principally.

http://www.worldwatch.org/system/files/AlterNet-SOW13-AL-102...

(Mostly the same material here: https://www.salon.com/2014/06/18/big_plastics_pr_disaster_wh...)

Her book and project, The Story of Stuff, are highly recommended.

https://storyofstuff.org/about/annie-leonard/
Also clean your smartphone. It builds up more bacteria than a petri dish laborant could hope for.
The problem with coming in later is that data models are hard to change once a system is built around them. Sure, a DBA might spend a few days optimizing what's there, but the structure of the model itself is something you'll have to live with for quite a long time. Getting it wrong at the start means pain every time you interact with the database.
I'm not replying to what you think I'm replying. To summarize: little plastic arms are not useful against dropping a phone from 150 ft. Because: 1. they are not made to absorb a shock that large, 2. even if, the phone would bounce, 3. even then, you're looking for a phone in a fairly large area. Easier not to drop it all of 150 ft in the first place; most people dropping phones do so from human-comparable heights, and that's where the little plastic arms are useful.

Clearer now?
Remember that in-universe those words were spoken by an arrogant super human who was hundreds of years old.
What's intimidating to me is that to make a change like that, you first need to get the code, get it and the tests running, and actually understand what the code does - and whether your fix has the equivalent result or is subtly broken.

They didn't just change a single line in an application, they wrote a huge benchmark suite and dug through miles of code to find issues like this. I've no clue how much time they spent on it, it must've been months.
Most Americans Think Facebook and Twitter Censor Their Political Views
Problem with Webpack is that they are allowing such a long dependency chain for micromatch when a simple JavaScript /regex/ expression could do the trick. Their blatant refusal to remove that dependency (as seen in the github link) quite clearly indicates their willingness to perpetuate this dependency problem.
Definitely padded the bank accounts of a bunch of law firms though.
TLDR - buy this ^
Well if he met me, he could add one more person to his list of people he has met over the years that meet his expectations of "full stack developer."

To be honest, I'm getting sick of the front-end/back-end bifurcation that I see literally everywhere now. I'm even guilty of it. It has this notion that you are either back-end only or front-end only. It really leaves no room for actual expertise that allows a software engineer to actually build software.

In fact, the terms back-end developer and front-end developer imply neither person on his or her own can actually build working software without the other. And that's total crap.

These terms started appearing more frequently in the mid-to-late 2000s and nowadays they seem to be all over. But back in the early and/or mid-2000s, "Web Developer" or "Software Engineer" or "Application Developer" sufficed and it was implied that you could build software from scratch, soup to nuts. Of course, in a large organization you had multiple "Web Developers" who surely specialized in one thing or another in order to help their comrades out so not everyone was doing everything at the same time to maintain sanity. But still, as a "Web Developer" it would be expected that you could build software and everything that entailed for the web. Not "Oh well I built the backend... now you just need one other person to do the rest."
This article is a defense of entrenched mediocrity.
Was the industry so pleased with the timelines and reliability of software projects a few years back that it seemed sensible to heap another career field's worth of complexity onto the developers?
How to Improve Performance of Galera Cluster for MySQL or MariaDB
A true 'sysadmin' in those days was not a pure-IT person, he was an expert of the systems

Back in the day these were called Systems Programmers but they’re a rare breed these days.
This is the first time I'm hearing about Snap. Could someone comment more?
Case Study: How Darren Grew His Twitter Following by 1,000% in 3 Months
Sort of, but you'll have to assemble several different libraries to make it good. It doesn't handle request validation, JSON serialization/deserialization, or databases well out of the box.

If you use Flask with Flask-SQLAlchemy be sure to use apply_driver_hacks to enable the pool_pre_ping option or you'll end up in production wondering why 1/3 of your requests are getting a bad DB connection from the pool.

Honestly, it seems like many somewhat essential libraries for Flask APIs are being maintained by one person on GitHub. I wouldn't want to put my faith in that for a core part of my business. Django has a lot more resources going into it even if it's not as powerful as SQLAlchemy or as simple as Flask.
Perhaps an average developer couldn't as the average is around $100k, but a realistically high earning one could. Consider someone who is a staff/senior staff/principal engineer at one of the usual places or someone who went through a nice exit. Forgive me if I read your comment too literally.

I think that's generally the conclusion that I come to: I'm very happy being realistically rich in America, but I'd much rather be in Europe if my financial situation were average for a software developer.
> Good developers can be passable DBAs if need be

This assume a developer is not a DBA. Or as if you can't be a good one.

I start with FoxPro. So databases is always first for me... to the point that I "mockup" the app with the database schema first.

So, I'm saying that for some people the database -> app is a straight, natural path. DBAs in the past was more about control the access to a central BD in a MAINFRAME. Modern RDBMS are very easy to administer and optimize.

In fact, I think that learn Java, .NET or C++ is far more harder than learn how use a RDBMS in full...
I guess you already read that part but for everyone else: yes, lets embrace os diversity.

I'm not against Macs. On fact I say: if possible give Macs to everyone at work who prefers them.

Linux is not perfect. My current Ubuntu has been particularly bad. (But that might be my fault as I got to the current state through unofficial states.)

I even grew an appreciation for Microsoft, partly because they changed a lot and partly because I learned a lot (about ABI stability, large scale software engineering, importance of documentation etc etc)

So lets advertise our OS-es but lets not pretend Mac or Linux is best. Not mentioning Windows here since they haven't annoyed me for a while : )
Speed is one thing, but the key value proposition of Keras for me that rarely comes up in these comparisons are Keras’s native utility functions, including easy and correct text tokenization/padding, easy OHE of categorical variables without using sklearn, and easy model saving/loading from an .hdf5 file. (Although I am not an expert on PyTorch and not as familiar with the ETL pipeline for that)
It pivots on what we mean by "understand fragments".

The average English speaker cannot make sense of Latin prose. Picking out a few words here and there, isn't the same thing.

"Quidquid Latine dictum sit, altum videtur."

All but 'Latine', and perhaps 'dictum', is gibberish to the average English speaker.
Are you seriously suggesting anyone who has renal failure shouldn't have children?
What next - siblings of renal failure should be sterilized because they might be at Y% higher chance of X unknown disease?

Your choice if you don't want to sign up for organ donation, and I respect your choice. Everyone should make their choices about their bodies.
However, your choices are coming from horrible misinformation.
> hand it over to someone less skilled

I'm mostly in Ops and I often find myself getting handed something from less skilled developers to run in production. It's frustrating too.
Part of the reason for Apple betting big on Intel was power efficiency. But with Ryzen going to 7nm before Intel makes it to 11nm(?) reliably, I have to think that Ryzen with integrated GPU starts looking damned attractive.
Hard to classify them as "vulnerable" given how successful they've been independently and they're privately held. I'd be "vulnerable" to the right eye-popping offer too, so don't bet on anything right now.
I find it some of the hardest documentation (close to AWS) to understand the best way to do something. I think it's great if you know what you're doing or you have a rough idea of what to do but need more information, but for someone new to the framework it makes me want to paper cut the webs of my fingers and bath my hands in vinegar because it would be less painful.
I thought I was going to be the only one to raise this issue. Not only are the advanced features of postgres unnecessary, these types of fleeting platforms don’t really need to have their histories maintained. HN runs without a DB just using flat files, IIRC.
If you have need living in China for 3 years, you are probably aware of how effective is the censorship there.
I don't want to give too much away but consider that if you start by weighing 6 coins against the other 6, you already know what's going to happen.
I'd think you could do warnings on this simply by processing a log of the queries, looking for query patterns that match common poor code patterns.

E.g.

SELECT id FROM table [some conditions]

followed by a number of

SELECT * FROM table WHERE id = ...

is one example of a anti-pattern that suggests that someone is doing an overly simplistic query followed by a loop. Similar with signs of triggering loading of related objects instead of a JOIN.

Doing it on the emitted SQL would also make it quite easy to make it reasonably ORM agnostic - it doesn't need to be perfect, after all, so doing relatively crude pattern matching ought to be able to find at least the more basic problems.
What are the bad bits? Why are they bad?
The question is simple economics, specifically game theory.

What's the contract between the parties? Is it one sided, and allows arbitrary modifications by the service provider? (Check.) Is the telecoms market currently in a pathological (unhealthy) state, due to lack of sufficient number of competitors, due to gigantic barriers to entry, due to regulatory capture? (Check.)

Infrastructure is typically something that benefits from standardization and economies of scale. The original network effect. Therefore it's very much a "natural monopoly". But combined with spectrum auctions, it's a proper state sanctioned monopoly, or in this case oligopoly.

The solution is to separate the raw technical network operation from all the other shit, and make it a true common carrier. The hard problem is of course the network evolution (maintenance, tower allocation [add new or remove old, what kind of tower, where, when], backbone management [buy new fiber optic or sell old, or downgrade, what kind, from where to where, and when]), but this should be financed by the operators, and it could very well be operator contracted (when one operator feels they would benefit from a new tower, they would request that from the shared raw network provider, and pay for it).

Of course, there could be incentives to help the roll out of new towers (so, let's say the operator that pays for it gets 1 year exclusive access on that tower), or that the operators must finance at least X new towers every year or pay a fine (but this must be formalized so they must spend X % of their revenue on extending the network to new customers, and at least Y% on upgrading the existing network), etc.

Ultimately, it's a simple question, that leads to a hard problem, with very good approximate answers. We know this shit, it's the economics of a market of fungible service providers. It's the shit that got people Nobel-like prizes in Economics, because it's easy to model and show what's going on.
For toothpaste, I had a look on the lush website [0]. For me to switch to that, I would be spending 6 times what I currently am on toothpaste, and would also need to travel an extra 3 miles to get to my nearest lush store.

> Just about all produce/fruit is available without plastic wrapping

Maybe if you're shopping in farmers markets. I shop in high street supermarkets, and it _isn't_ available. I have a choice of buying a 1kg bag of onions, or not buying onions. I can buy a 3 pack of bell peppers, or not buy bell peppers. I can buy a 6 pack of Golden Delicious apples, or I can not buy apples. I do try and buy less packaging, but unfortunately the odds are stacked against me.

[0] - https://uk.lush.com/products/tooth-fairy
Apple cannot fight a war on two fronts, patent trolling and innovation Alzheimer's.
I can tell the ages of people posting on here from their comments.

I love Berlin because of the nightlife and culture. 20s.

I love Berlin because of the free schooling. 30s and 40s.

I love Berlin because of the free healthcare. 50s+
coinbase already has horrendous customer support. I wrote up my experience and findings of others on twitter in this blog post in December https://medium.com/@mseiler1/coinbase-support-is-non-existen...