skysight-inc/HackerNews huggingface dataset:
The indignation seems misplaced. Time tracking seems pretty common in the industry, whether it be mandatory or voluntary. Several places I worked had detailed time tracking, and it was pretty informative/helpful as a tool to manage your own task prioritization. It can be pretty eye-opening to sit down at the end of the week and actually take stock of how much time you spent coding, thinking, in meetings, getting coffee, screwing around, etc.
Historic Rejection Letters to Women Engineers
Yes, I've seen this syndrome coming from (pretty senior) management far more than from developers. My suspicion is that it's more about padding the CV than just "feel[ing] more important" - they may well be behaving rationally at the individual scale, they're just responding to perverse incentives in the job marketplace.
If you're searching across a whole project, the server is footing the brunt of that. it's only sending back the results. That's not usually a lot of data, so your connection would have to be in the kilobits to be that big of a burden.
JavaScript LowerCase HeadLine Converter Tool
They're an RDD shop (Resume Driven Development).
Emailing back password in plain text - hey this is the password you've just set, don't forget it!

I've only had it happen to me about 4 or 5 times in the past 15 years or so. But it makes me so disappointed each time that I literally want to find that developer and knock him/her out with the ugliest hammer I can find.
Is it your opinion that it is better to spend resources in ignorance, possibly harming, helping, or doing nothing, than to allocate them meaningfully with full knowledge?
Proxmox 2 Nodes HA Cluster on Hetzner
Looking for about 2 months now for any information about running a High Availability 2 Proxmox cluster on Hetzner, and found complicated warnings from fencing, wrappered switches and so on, what the problem with hetzner ?
But, that's still trusting the provider. The provider is likely to compute it at upload time and then store in meta data. So, having that meta result returned is no more proof your files exist than listing them.
Maybe Microsoft Support just thinks Canada is America's hat?
This works using the bitcoin blockchain and is a great example regarding the usefulness of blockchains.

I mention this because in the previous threads regarding crypto currencies, people were asking for some value-creation technologies based on blockchains (other than speculation and money laundering)
Here's what I see when I'm logged into their website on IOS

The camera icon in the centre (much like the app) is what you tap to start the process of uploading your image.

https://postimg.org/gallery/ctpt4i50/
if NATO doesn't defend the Baltics the whole alliance falls apart.
Had to pay, but there was an actual menu to order from, unlike an airplane with one (or no) meals.
Agreed! This falls into the "weak product management" category imho.

FWIW I think most devs could learn how to push back on poor decisions like this made by non-technical managers as it really shouldn't be the manager's responsibility to dictate technology choices for a solution. It should be their responsibility to push the dev team to make tradeoffs in order to achieve a business result.

Devs who are good at understanding the business objectives and pushing the non-technical team to make better decisions are both wonderful to work with and command higher salaries / fees.
First thing is first, you are learning a new stack, you probably have coworkers that know it better than you, so you have a golden opportunity to kill two birds (gain favor w coworkers & learn fast) with one stone!

Do not bother your coworkers with endless questions or interruptions, but try to use scheduled times to discuss how you're going to build things. In an ideal company, you shouldn't be building things in a bubble, there should be multiple team members ensuring quality instead of one or
two brains. (Also ideally coworkers should be trying to learn how you think so they can best tailor tasks to you)

The hardest part is continual, backbreaking improvement. It becomes easier as you keep doing it. I recommend getting a twitter and following everyone vocal in the area of the tech stack you're working on AND people who work on the same problems as your company (double reinforcement of shared knowledge in your industry). That way you're aware of the current problems that may arise (instead of being left in the dark), trending new ways to do things, counterpoints of why you should avoid some new trends, etc. Scour the internet for resources, such as HN of course, but also popular see sites, subreddits related to the stack, IRC channels, and follow the Github projects of the tech stack if possible (lots of discussion and examples are there!).

I like books. I spend thousands of dollars on books a year, but books on a tech stack rather than development practice will become quickly outdated, and can learn just as much online as you can in a book on a tech stack. I will only buy a tech stack / programming language book is if the language is hard core or if it is new & emerging with a smaller community.

I'd also recommend taking extra time to analyze and plan before diving in. Just sitting for maybe an extra 3 minutes allowing your mind to clear so you can put things together in the right way. Your goal is to become opinionated and knowledgeable faster, so taking the time to get it right early on is permissible.

Finally I recommend something that others won't tell you. It's to become a super fan of the stack (how) and company's mission (why). Your newly found enthusiasm would be a superb speed boost to your goals and add increased visibility to your efforts.

You will not instantly become productive or enlightened, but the fact that you're seeking to be better (yay enthusiasm) does increase the likeliness that you will succeed.
Everything about Bitcoin, from the original software up, is built by amateurs from gaffer tape and string. (Bitcoinica->Bitfinex and Mt. Gox were literally "I know PHP, how hard can writing an exchange be?") It's reiterating the history of financial systems as well as financial regulation, in fast forward.
Good thing we can max out all the good genes. I suppose it will have secondary effects but in small steps it should work.
Now imagine that to be hired as a carpenter you had to first prove that you have worked on dozens of pieces of wood before anyone would even consider you. Of course, the analogy falls apart here because we can expect most carpenters to have produced finished products, but most finished software products are highly complex and can take years to complete. Worst of all, these products exist in a marketplace where cynicism reigns: "Why did you build that? We already have three hundred of those. Quit reinventing the wheel!"

Do we complain when a carpenter builds a nice stool because there are already enough stools in the world?

Many companies now expect a GitHub history, as if that alone determines your value. It's no wonder people publish everything. They need to establish that they're doing something, even if it isn't master level "carpentry."
SQL Server Window Functions in Action
This is a bad idea. Definitely well intentioned, but has a lot of bad side effects. Especially at big companies, I was instead actively encouraged to dive right in, make very small changes to existing production code & submit it for a code review. That gets you started in the right direction asap, because the feedback is direct - its pertinent to your code that you wrote, so you feel it viscerally & begin understanding the code even though 10 minutes back it was an opaque mudball.

If you become a waterboy, you will definitely be appreciated by the team, productivity & morale will go up etc - But you personally didn't sign up to be a waterboy! You came to be a player. So play.

You can't go from being a standup-summarizer or infra-support-guy to your regular senior developer role. If you are any good at those ancillary roles, you will be playing those roles for a long time. Every day doing infra is a day not doing regular dev - that's just the way it is. I have been there & its not fun. These ancillary roles have a way or morphing into a fulltime job, and soon that's what you'll end up doing.

This isn't WMA/CAA where you start in the mailroom and few years later you become Hollywood's top producer greenlighting 100 million $ movies. It simply doesn't work like this in tech companies.
Why are you telling me what people have in 2017? No one is saying that USB-C is the standard now. Although in thin laptops it will be the standard this year. I'll be using my "legacy" USB stuff until it dies too.

The point is that market is starting to adopt USB-C, and everyone should be ready for the transition. I want a future port on my new computers, which will have a 5-10 year lifespan. USB-A would be nice too, but if I can only have one type, I'll take the future port.
Yes. Don't forget "CV-first" development is a thing.
One word: Clojure.
Multiple Choice Questions on C++ Operator Overloading  – InfoTechSite
This is kind of nice:

https://www.craigmurray.org.uk/archives/2017/05/roger-moore-...
Perhaps you haven't spent enough time reading into Kafka? It solves very different problems than the RabbitMQ/Clery "worker queue" pattern you're referring to. That doesn't necessarily mean people don't use Kafka for the wrong reasons.
Since we've eliminated so many predators, hunting is necessary to control populations. I would however prefer it if we reintroduced natural predators instead.
Reporter decries company for prohibiting its employees from discussing company business with reporters.
> do Americans learn about Dunkirk

There's a film coming out this summer about it.

Part of Granddad's unit was at Dunkirk (Cheshire Regiment) but he was not - he was in North Africa.
One problem I've noticed is that there are no good "medium data" tools.

Column stores are crazy fast, but there isn't much simple tooling built around things like parquet or ORC files. It's all gigantic java projects. Having some tools like grep,cut,sort,uniq,jq etc that worked against parquet files would go a long way to bridge the gap.

Something like pyspark may be the answer, I think it may be possible to wrap it and build the tools that I want.. like

find logs/ | xargs -P 16 json2parquet --out parquet_logs/
parquet-sql-query parquet_logs/ 'select src,count(*) from conn group by src...'

I've been testing https://clickhouse.yandex/. I threw it on a single VM with 4G of ram and imported billions of flow records into it. queries rip through data at tens of millions of records a second.

Edit: another example... I have a few months of ssh honeypot logs in a compressed json log file. Reporting on top user/password combos by unique source address took tens of minutes with a jq pipeline. The same thing imported into clickhouse took a few seconds to run something like

select user,password,uniq(src) as sources from ssh group by user,password order by sources desc limit 100
maybe it's willing to loose points to erase uncertainty. Lee said AG took a smaller position on the top, eating the two stones, in order to simplify.
What's getting stored in a blockchain?
Depends on not only the input, but also the output. What kind of analysis do you to perform?
That's a good point. It's also worth considering this: isn't there a difference between having 90% of a forest left and 5% of a forest?

I know that it's not exactly fair, but that is more-or-less the situation we have now. There were once vast swaths or virgin forest, and now there is very little left. Are the situations the same? Should people behave the same now as they did then?
Ultimately everyone needs to decide for themselves.
Building a realtime React VR app
> Developers can build apps on this new internet by downloading the Blockstack Mac or Linux app (Windows coming soon) and by using nothing more than your existing Chrome or Safari browsers.

Why Chrome and not Firefox? In their context, the later makes way more sense.
I've worked in a similar situation -- a transaction processing system with ~1M tx/day and ~2TB total data. They used 15 Cassandra nodes and a monster Redshift cluster (>64 CPU cores, ~512GB RAM, 30+TB disk) for the OLTP and OLAP queries. I almost can't put Cassandra and Redshift on my resume because when more knowledgeable people ask about my experience with them, that pathetic use case makes me look bad by association.
I bought a first gen Apple product (against conventional wisdom), and seem to have gotten a lemon.

Most of the stuff was not avoidable- image retention on the screen, worn out battery, defective motherboard, etc.
I posted about some of my passengers' justice-induced traumas:

https://news.ycombinator.com/item?id=13286085

Punishment is always counter-productive to correct the behavior of people who are "drowning": addicts, members of the under-class, children who've yet to fully mature (brain is still developing until 25 years), etc.
Your example would actually be part of a different mailing list .
See https://www.bloomberg.com/news/articles/2017-05-23/at-google...
Clearly the runt ate the orpington's soul.
Unless I can unplug the WAN connection on my router and connect to your product instead, keep in mind that you haven't invented the next internet. You might be able to decentralize the worldwide web of HTML pages and hyperlinks, or invent another protocol that can be encapsulated in TCP/IP packets and ethernet frames, but the internet (the graph of inter-connected networks that speak common protocols) is still a fundamental requirement for your product, and the metadata associated with those stacks is still very real and trackable.

To that point as well, the internet already "works how real life works." Sick of Company X and the way their business treats employees? Shop elsewhere, remembering that it won't be as convenient with fewer choices. Sick of Google tracking the websites you visit? Use a search engine that doesn't track you, remembering that they probably can't pay as much for great engineers.

It's Conway's Law. We are largely constrained to create systems (including the internet) that mirror the organizational structure we're a part of. Yes, we can evolve and revolutionize occasionally, but it will always mirror "real life" because they will always influence each other.
AWS is launching instances from 4 to 16TB of memory in the coming year: https://aws.amazon.com/blogs/aws/ec2-in-memory-processing-up...

Even terabytes of data isn't "big" anymore.
That metonymy argument would be more correct if we knew that the technology existed. Patents are filed all the time for technology that doesn't really exist (or maybe even can't really work).
Why not just go to their documentation?

http://kafka.apache.org/documentation/#introduction
What if you're working four days a week?
i think 4 and 5 are using skylake and kaby lake which is a minor perf improvement. the cpu comparison is not very interesting. we will have to wait for the next intel 'tick' before cpu comparison becomes meaningful again.
Things that are important ending up in public history is the mess in the first place.

JIRA is typically secured. As are VCS. As are Slack channels.

What is not secured are the developer machines...
How jeans conquered the world (2012)
While I tend to start at the CATO blog I usually end up one of the sites they point too. Libertarian sites like CATO have always been interested in the abuse and injustice of the system. I know there are some knee jerk not fans of CATO but you really are missing out.

to summarize our times the simple comic on this page illustrates how the system can threaten everyone https://www.cato.org/blog/when-our-rights-become-crimes

even reason.com is good for much. still it comes down to reading all sides and you will see a common theme even they are coming at it from different directions. the thing to remember is government segregate us more than anyone else and politicians play off the fears of one group versus another to perpetuate the system.

Favorite site for police issue and how preposterous the system is.
https://www.policemisconduct.net/
LeEco collapse continues as CEO cedes control; 85% of US workforce to be cut
I'm biased in that I've been doing nothing but Hadoop consultancy for almost 10 years now.

I have done maybe a hundred to two consulting hundred projects based on Hadoop (as you can imagine it's mostly short-term and troubleshooting stuff) and am a ASF committer myself. So take this with a grain of salt.

I've seen the kinds of projects the article and lots of people in here refer to and I agree with lots of what's been said.

I also agree that Hadoop (the whole ecosystem) probably not has a single "best of category" tool that ticks all the checkboxes but IMO that's totally missing the point.

What it gives you is:
- (Mostly) Open source stack (compare that to your Informatica/Talend/IBM stack that big companies have and not to your Python jobs they don't), lots of the code is crap (see my Apache JIRA history) but it's there and you can attach a debugger to your running cluster, that's fantastic and very hard to do with e.g. Python (at least I'm not able to find good ways of doing it)

- Proven technology, it works most of the times and if not there's tons of SO answers, mailing lists, books.

- All the boring enterprise stuff: Encryption at rest and on disk, strong authentication, strong authorization, auditing, high availability, failover etc.

- Integration into Monitoring & alerting tools, distributions figure out the important stats and thresholds for you

- Mostly easy to operate these days even at large scale thanks to Cloudera Manager et al. - no need to manually run/install stuff

- "Coolness factor"

- Costs way less than established tools with e.g. external storage filers or similar specialized hardware

- It's not trivial but also not super hard to find people with Hadoop/Spark experience

- Existing purchasing agreements with Hardware vendors or Cloud providers

- Business/C-level gets and supports it

Edit: Three more I thought of:

- You can buy licenses and support for the tools. Both of which have been discussed multiple times here on HN, a donation doesn't work that well for companies

- You can buy indemnification from license problems from at least Cloudera but I think Hortonworks as well

- If the same stack has been used elsewhere in the company already chances are there are processes in place, someone has already vetted it, done the open source checks etc.

See what I don't mention are things like performance or absolute money amounts or even the amount of data (as the whole ecosystem is much more than "big data" now) etc. as we see surprisingly little projects that care about specific SLAs or features. It's all relative.

That said: At least 50% of the projects would still be better served by a simpler solution but that still leaves a whole big chunk of projects where Hadoop makes sense for other than technical or monetary reasons.

But I very much disagree with this part of the post:
> The only benefit to using Hadoop is scaling.
Very cool, I really like this idea of Nomic-style open-source code governance. I previously built a similar project: https://github.com/botwillacceptanything/botwillacceptanythi...
Sent you a note :)
Can't even get people to migrate to ipv6 and they expect anyone at all to switch to a blockchain browser based internet thats 100 times more complex? DOA.
Actually, there is a lot of literature that indicates the opposite. Informing people of bias makes them more susceptible to it (by making them better at rationalizing away their bias). And the backfire effect causes people to become more certain of wrong opinions when presented with evidence to the contrary.

The idea that intelligence produces rationality is a myth.
Absolutely. The JVM is great, and JVM languages like Kotlin and Clojure. Even modern Java is a good language. I'm not arguing that Java hasn't come into its own as a good language. My point is that the Java I cut my teeth on? "Java 2"? That was bad.
You work for Ikea? The problem is that nobody is planting them back.
This is really cool thanks for sharing.
With the MateBook X, Huawei finally has a MacBook to call its own
That's a really good deal - mind sharing the manufacturer?
At The Dawn Of Recorded Sound, No One Cared
I don't deny that Kafka solves different problems and has excellent performance at high loads (100K msg/second).

>> That doesn't necessarily mean people don't use Kafka for the wrong reason.

Exactly what I meant.
Recent HN thread that ended up flagged, including a comment from a Googler: https://news.ycombinator.com/item?id=14394600
> Lenovo will be among the first OEMs to provide hardware with Windows 10 China Government Edition preinstalled.

eBay?
This is an important point that is not clearly addressed.
So majority of Windows software has HiDPI support?
You say salesmanship I say companies resistive to change ;)

The point of the manifesto and of training is to present the idealized form. All decent Scrum training will point out that, when the rubber meets the road, there are going to be compromises.

The idea is that it's more a frame of mind than a rigid system. If you approach the "cold, hard reality" with that frame of mind you'll still see improvement.

I'll give you a common real world example: having simple timeboxed sprints and daily 10 min standups is all many companies end up doing.

That's a shame but at the same time now that team has better team communication and better tracking of progress.

Will it be as good as it could be? No. Is it as bad as it could be? Also no.

It's a trade off.

The salesmanship that pisses off so many devs is because a truly Agile workplace requires buy in from all levels and know what helps get buy in from management? Certification, training, webinars, and enterprise-y biz-dev seminars.

There's a tendency of developers to think that every part of something that applies to them should be for them, but that's not true. That salesmanship is not aimed at you, it's useful training for you (I'm doing CSD training this summer for example), but that part is aimed at other parts of the company.
Is this republic dying?
Sure. Though there is a culture cost to an environment where you actually fire people without cause.
I learned Java after learning Python and C++. Even at the time, the combination of static typing and no macros/generics/templates was cringeworthy. Then C# came along with Generics and the Java leadership finally admitted they had a problem.

To be blunt: this is not hindsight. This is me remembering working with Java in the early 2000s. These were things that jumped out at me as an undergrad student as obvious pain-points in a new language I was learning that were not present in other languages I had used.
The biodiversity contained in current old-growth forest might not "grow back" for quite some time though.

In any case, we have the ressources to address both pollution and the destruction of forests, there is no need to decide between the two.
This could have been worse. I was using Crashplan and tried to add an ignorable directory in the web panel, which had no flags or warning labels or anything around it indicating that it could be destructive. The web server had some kind of error and when I reloaded the page, my settings were wiped out. Several hours later I got an email that all my backups were going to be deleted by 5pm. The email was received at 5:20pm. Customer support basically just shrugged it off, and I was an ex customer by the next day.

Shit happens, but that was particularly egregious. This is why you should have multiple backup methods in place, and if you've never restored one, you don't have a backup.
Not just backups. Restores. You need to test your backups by periodically testing your restore process to ensure the backups are actually any good.

Test your restore process periodically!
Electronic Lottery Tickets as Micropayments