skysight-inc/HackerNews huggingface dataset:
The problem here is not the tool but the process that comes with it. From the managers in the bigger company's perspective integrating your team into the larger structure makes a lot of sense. What they are probably missing though is the impact that doing things their way is probably going to negatively impact your team.

Opposing the tool is not really going to get you anywhere. From the outside it will just look like you are resisting the integration with the bigger company and all the baggage that is going to come with not being "a team player".

For entertainment purposes only: fight fire with fire. Make a case for improving developer productivity by implementing a ticket quality score and use it as a metric. After all, the better the ticket the faster you can start work on the problem, rather than having to go chase down all the issues and requirements. Management will be rather annoyed at you flagging all their one sentence tickets as inadequate. As I said this is for entertainment purposes only. It's fun to make a point, but push quickly becomes shove.
I'm somewhat torn about that idea. Here's why.

My story is that I composed a django+angular app. Rather than replace the jinja templates, I treated them as a noop and wrapped the angular in verbatim blocks. Was a rather trivial bit of code and "Just Worked."

For the same reason we look to circumvent jinja templates now is broadly why I don't think python web frameworks should be in the business of servicing one particular SPA framework. I can see some slight benefits in e.g. integrated routing support, maybe some level of model integration, but I'm hard pressed to think of how one could gain _huge_ conveniences without a real reorientation of how I look at the separations between the python and JS sides of things. (which is largely why I'm curious if I _am_ looking at all this in a very amateurish way)

Anyway, I should probably take this as a reason to learn more than nothing about Rails, since all of the above may be answered by seeing what their end product looks like.
We should be worried about locking our workflow to a specific provider. The fact a provider makes it easier or provides tools in itself isn't lock-in.

Even then we shouldn't be particularly worried. Vendor lock-in is an unusual problem; deciding to change vendor is rare and if there's a good reason to do it then it's worth spending resources. The only time it's a real problem is when you absolutely have to change and you don't have the resources to do the necessary work.
I like Dijkstra's algorithm for finding the shortest path between two nodes in a graph.

It's not so much that it is "beautiful", but it is a remarkably simple algorithm that a human can follow manually. The reason it is efficient is easily understood (it's easy to see how we are able to "finalize" nodes because it's obvious there is no shorter path to that node), and it takes what would otherwise be a complicated task and makes it manageable.
I've had a pretty similar experience. Get exercise, sleep, food and hydration under control, then (in my case) medication helps me make the most of that structure.

I actually just wrote a giant post [1] about what I've learned about managing ADHD so far. It focuses on the core stuff, but I want to follow it up with a breakdown of how books like Deep Work (e.g. Flow; Farsighted; Thinking, Fast and Slow; How Not to be Wrong) have made a difference for me.

[1] https://medium.com/@sashacollecutt/life-with-adhd-a61cae5a5b...
Our war on fish and how they feel about it
To add to your coment, depending on the company, moving a lot of $$$ to capex is incredibly important for management.

If anything you should embrace Jira and look for ways to help get things classified as capex. Ask for a meeting with accounting/finance to fully understand it.

Just think of it as learning a new skill.

For the people saying to look for another solution, I would first figure out how much work they put in to selecting Jira. It was probably a big decision making process and you may be too late to make a change.
Euclid's GCD algorithm, and Russian peasant multiplication.
While I agree React isn't the issue here, you chose horrible examples. Loading Facebook on my computer (especially trying to open a chat window) brings my computer to a knee. And using twitter on mobile browser you quickly learn how the spinner looks.
Western media has sort of an honor code not to engage in such actions. We traditionally prefer people to find our creative works because it's good and high quality, not because we gamed some algorithm.

That being said, it's entirely possible for someone outside of these organizations to start something like Chu Chu TV in the United States. However, it would probably face harsher criticism.
The rise of non-microservices architectures
Why would that matter for learning typescript..?
Lidar can get into trouble with obscurants. Don't get me wrong, lidar is an amazing sensor, but not perfect
I've been just draw a .gitlab-ci.yml file with random sleeps. Hell, I might expand upon that and make the sleeps sorta simulate the real thing but on a faster timescale for demo purposes.
const arrify = a => a && (Array.isArray(a) ? a : [a])

vs. introducing a potential attack vector.
Cybercriminals?! What a poorly written article. Multiple “firewalls” in a home and nothing about VLANs?

That being said, it is good practice and something I’ve implemented in my home - thankfully my Unifi / pfsense setup makes this very manageable.
Speak softly and carry a big stick.

VCs constantly talk about supporting entrepreneurs through tough times, enabling creativity, building amazing companies, etc. They're not lying -- they really believe it, and it's an important thing for them to believe.

But while they say all this stuff, they're also human. And humans follow their incentives. They do that before they do anything else. So your job is to make it easy for them to act ethically.

That means talk the talk -- you want to build a great product, scale it to an amazing company, hire a great team, etc. That's the only thing you care about. Building a great company that builds amazing products and makes everyone lots of money. But act game theory. Have lots of great alternatives to negotiated agreements with any given VC. Put yourself in a powerful position where you can get favorable terms. Don't give up power/equity on the assumption that "it doesn't matter", or that they'll act magnanimously, or anything like that.

It's way, way easier to have a lovely relationship with people when you're in a position of power. Put yourself into that position.

(There are some investors you can unequivocally trust to act their talk -- notably YC, winfunding, and a few others, but don't rely on that as a general rule)
In a fresh create-react-app project, their getting started example that includes only a button results in a minified js of 570K. Apparently the whole of Blueprint.js is included as a dependency. Shouldn't tree shaking take care of this seamlessly?
I've wondering why that's been true for 10 years and yet noone's even close. Cuz if they were waiting for AMZN to make a big mistake, they waited too long.
I continued to stick with short stories by Chekhov and Gogol after that.

If that's your fallback position on difficulties with Dostoevsky and Bulgakov, you're pretty much killing it at learning Russian. And it's not like those guys are going anywhere either.
Oh good, the machines are already perfecting the victory dance they will perform on our dead bodies.
Word. Solid advice. When you delegate all the decisions to a person looking at the global maxima at the expense of the local needs of your team you will not be happy with the results. For as long as you delegate this task, you will be unhappy with Jira. As soon as you take an active role, the perspective on Jira tends to change.

It's a good example of how being the change you seek changes your POV on something.
http://archive.is/6Cb2I
I recommend try it - if you dont succumb you'll have immunity for the very long after that.
Damore clearly wanted an open and honest discussion, which is why he wrote so politely and provided citations for all his arguments.

The resulting meltdown and repetitive lying about his memo just goes to show how right he is. Nobody has successfully defeated his arguments which aren't even complicated, they're obvious and common sense. Instead they just try to shoot the messenger.
A child's cognitive recall abilities and associative thinking are super small when compared against an adult. Because of this, there typically isn't any room for additional information besides what's covered in the school day. The issue with video games is that some games take advantage of our attention span. In children, especially those without time management skills, the mind chooses between the instant gratification of the video game or the delayed gratification of studying for their school work.
Show HN: Web app for creating labeled data sets
Make a good pitch
https://blog.ycombinator.com/how-to-pitch-your-company/
A good path finding algorithm makes me happy. One that balances performance and efficiency.
Unix in East Germany (1990)
I see two practical issues with network segmentation:

1. It breaks broadcast/multicast, e.g. for your phone discovering your chromecast. A number of IOT devices need to be on the same network as the devices from which you want to use them.

2. It’s way too complicated for novice users to set up, so it cannot be vital for making IOT devices secure.

Personally, I like to keep all my devices (whether IOT or not) patched (ideally because they’re auto-updating). That way, if a lightbulb gets hacked, it can’t get to my backup drive either.

That being said, I do think there’s some value in throttling bandwidth for IOT devices. It’d need to happen automatically (which makes it hard), but would nicely prevent DDOS attacks.
> It's a reasonable question - but the price can never be truly "free," because there's a cost to investment / build that product - meaning costs are non-zero.

Those are fixed costs which can be amortized in other ways.

For example, Google could make both the OS and the hardware to sell together, like Apple. In fact, they do, with the Nexus/Pixel devices. Once they've done that, the OS development is a sunk cost. Giving it away to others or not has no effect on cost, or has negative cost if some of the others make contributions that you can use on your own devices without paying to develop them internally. And it grows the ecosystem your products are a part of, which is a valuable service the other vendors are providing for which some remuneration is appropriate, which could offset some or all of the cost of the software.

Moreover, software costs money to develop, but how much of the development cost should be apportioned to each unit? That depends how many units there will be. Not have been -- will ever be. This value is not known and can be arbitrarily large. For something like Android it is very large. If you amortize the development cost over the number of devices there are/will be, the cost per device is negligible -- small enough it would be eaten by transaction costs if you tried to collect it.

And claiming that companies can't give away software because they're large is clearly bad policy. It would imply that e.g. they can't contribute to Linux.
Why shouldn't parents trust a multibillion dollar company that employs literal geniuses when they say "hey, we have some videos that are suitablefor children"?

Until you've tried it you don't know how terrible it is. And by that time it's normally too late.
For the final customer, yes.
Spin up a simple one board kanban project, use the new roadmaps in Jira cloud to show the epics to management and move things from backlog to in prog to done. Add tempo for time tracking if you need to show the accountants how much work has been done.
Toward Community-Oriented, Public and Transparent Copyleft Policy Planning
I guess your assumption is that every one gave up on buying car and instead every day they drive to work. The impression i have from my friends is different: they use lyft when they cant take car or want to drink while with strong economy the can afford having car as well. I dont know any single person who would sell their car because they can travel with lyft to work every single day.
They packed SF like a clown car, of course all commute times went up. Not sure how it is Uber's fault.
(disclaimer: I don't know how this looks) if you follow the old-school web app model, you're working on the basis of stateless requests. This means that if you want to make a multi-page form, you have to build up coordination mechanisms between pages.

In something like an SPA, you end up having frontend state, but you're lacking the corresponding backend state. There are a lot of times where I've wanted to do something in the backend like:

first_response = await render('first_form.html')
if is_valid(first_response):
final_confirmation = await render('second_form.html')

(This is obviously more conceptual than actual code, since actual code would require suspending python VMs for some unknown future)

In a framework that is more amenable to the fact that frontend clients have state, you should be able to write out multi-request flows more easily. Perhaps with some base notion of a request trace (with the understanding that the frontend also need to send extra info to identify itself).

Websockets are something interesting, but it doesn't quite enable this. And it won't be easy to get right. Failure cases in particular will require some coordination.
Breadth first search is simple but effective
That or they have already made up their mind and are just looking for an excuse to reject the candidate.
Diffie–Hellman. I know that cryptography can get much fancier and more clever, but Diffie–Hellman took a concept my intuition told me was impossible and showed that it's possible in a really simple, elegant way. Learning about it was the first time I realized how beautiful the math behind computer science is.

It's also a great insight into just how fundamental the concept of computational complexity is.
> Batman The Animated Series

That one does get somewhat violent, though.

And be sure to show them Batman Beyond when they get older. It's my personal favorite of the DC Animated Universe.
Wouldn't that goal (qualification of spend as capex) be solved better by timecards? I don't see how a bug tracker helps unless you abuse it to be a timecard system.

Of course, timecard software can be awful too.
Myers Diff. It hits the trifecta:

1. An irrefutable improvement over the state of the art.

2. A short paper which can be understood after only a dozen readings or so. I mean really understood, with visualizations and everything.

3. A practical algorithm which can be implemented by nearly anyone (even me).
I think it's a beautiful, thought out, polished and well built set of UI components. If that's what I needed for my next project, I wouldn't hesitate to use it. The docs are excellent too. There's so much attention to detail here. There's an immense amount of love poured into this project, even the code snippets are interactive.
Interesting that GitHub is continuing to still actively develop independent features after the acquisition. I almost started to say that this seemed like a pushback against Microsoft’s newly-rebranded Azure DevOps before I even remembered...
I don't think you can ever really reverse anything in git either. Reflog has saved my ass a few times.
BOGO sort! /s

I really like backtracing algorithms used to solve huge graphs without actually visiting all nodes. Pretty elegant IMO.
Sleep sort :)
The cost of firing Damore was much, much higher than that.

It sent a message to the entire world that Google is staffed by extremists who systematically cannot be trusted to provide unbiased services or search results for anything involving women or feminism. It caught the attention of conservative politicians. It killed dead the idea that Google is run by logical, data driven people (as Damore's memo was basically a big pile of data and studies), and judging from what my friends who still work there think, it created huge cynicism in the developer workforce too. It very much did not "appease the devs" unless you are naive enough to believe that Damore is some outlier in disliking diversity programmes in tech firms.
While I agree in the theoretical sense, that does not reconcile with practical reality.

Much like Communism and Libertarianism being great in theory, but failing in reality.
> I guess this includes watching TV while also doing other things

Exactly this. Some of my family members leave the TV on while doing other things "for the noise". Before the internet, you usually had what was either on TV or on the radio in terms of instantly finding background noise. TV was generally considered higher quality by most.
Because the outside air is polluted and having to wear a air filter while exercising is unpleasant.

Because I have to watch out for traffic and pedestrians outside, and driving to a cycling/running path takes about 15 minutes anyway.

Because looking at healthy, fit people exercising gives me more motivation to get in shape.

Because I can devote more attention to my audiobooks than if I was exercising on the streets.

Because the gym is in my apartment complex, so I just go downstairs and walk 2 minutes to the gym.
Which conclusions, exactly?

He claimed that writing the memo would put his career at risk because left wing opponents would attempt to purge him. In fact the memo wasn't even primarily about gender, it was about anti-conservative bias at Google. This claim was proven entirely correct by what happened next.

The reason he used the phrase "cultural Marxists" is because Marxists have historically relied heavily on purging institutions or ideological opponents, suppression of speech, insistence on conformity and relentless lying about people they dislike. Given that all these things have happened to Damore it appears to be an apt analogy.
Really? that's why people wanted to advertise on FB? Not because it's the most used website in the world huh?

All numbers from advertising are wrong.
I've worked for few different companies where some development groups were producing negative productivity, and others were producing positive productivity. Consider that one "profitable product ruined", and one "unprofitable product made profitable", or equivalent metrics.

What's the productivity ratio between -1 and +1? Is the first team "less productive" than the second team? Certainly. Is the second team "twice as productive" as the first team? I think the answer is "infinity", so "over twice" is a good summary for people who intuitively distrust "10x" as a number.
Jira is pretty cancerous. It will likely lead to hundreds of developer hours wasted on buggy, complex UI, new processes which are put in place because the features exist to support them, and eventually a slide into a multi-atlassian-product cluster of almost-working cruft.

That said you're SOL because you don't have a solid set of tools in place today. I know large, distributed teams who use github effectively for example and they have the processes and cultural inertia to make it work, but it doesn't sound like you've even got a solid home-grown alternative.
The Largest Open Goal in Cyber Security (isn't What You Think)
You are right, Google did not intended Android to be a move against Apple from the start, this happened later after iPhone release.
I am also remembering about some emails between Steve Jobs and someone at Google but I can't find them, anyway Google is paying a ton of money to Apple to be set as default search engine, if Apple gets a bigger market share then Google will have to pay even more.
I was curious so I checked out their Github page. I found this example:

classNames('foo', 'bar'); // => 'foo bar'
classNames('foo', { bar: true }); // => 'foo bar'
classNames({ 'foo-bar': true }); // => 'foo-bar'
classNames({ 'foo-bar': false }); // => ''
classNames({ foo: true }, { bar: true }); // => 'foo bar'
classNames({ foo: true, bar: true }); // => 'foo bar'
...
var btnClass = classNames({
btn: true,
'btn-pressed': this.state.isPressed,
'btn-over': !this.state.isPressed && this.state.isHovered
});

Look like the button example is a good enough convention for me, I don't need any of the other conventions. Can anyone tell me why this is not sufficient?:

const classNames = (pojo, c=[]) => {
for (let k in pojo) if (pojo[k]) c.push(k);
return !!c.length && c.join(" ");
}

Do I need array-flattening support, multiple argument support? The size of this library probably comes from it supporting a handful of different coding styles. I would say the size (50 lines) is too large, if anything. Dependency worthy? I'm not convinced. I am very much so against requiring trivial utility functions from other people. Roll your own if it's trivial! It's better than depending on something over the network.
Yes the internet was the key. Everyone has been taking advantage of new technology to sell products since the dawn of commerce. What made Amazon great was an understanding of how the internet could be exploited.
Same here.

The funny thing is, some people have a hard time losing features no matter what. There are alternatives to MagSafe, such as the Griffin BreakAway, but they don't buy these.
The term, systems engineer, had different interpretations depending upon the environment and context. In my experience, in IT the term could be better described as systems integration, i.e. building systems out of sub-systems. I have engineering degrees and decades of experience and yet I wouldn't claim to know more than a fraction of what you allude to in your question.

Very loosely speaking there are there major areas of systems engineering, mainframe based, large-scale Windows enterprise server based and Linux cloud based. The technologies differ greatly across these so you probably should choose a single area.

The common ground amongst these three areas is network engineering. Any large scale environment comprises complex interconnection of nodes, switches, load-balancers, etc.

If I were in your shoes, I would find a job with a medium sized systems integrations consultancy and then develop my skills in one area at a time. Over time you would end up with a comprehensive knowledge across the many areas.
> The difference here is that Apache didn't shove you a PlayStore, maps app and a browser in order to use their libraries.

That's a completely independent complaint that has nothing to do with Android being available for free. You would have the same tying objection if Android cost money, right?
I think Krylov subspace methods are particularly sophisticated and elegant, and they come with the added advantage of being best-in-class.
What products has she bought?
Having two distinct routers and physical devices just isolates each network that much more. A single device is still exactly that at some point, and in such cases there is always the possibility of an exploit that could compromise the device fundamentally.

I think the author is just advocating for a very locked down approach but I agree it is not feasible for most folks.
Before you request a pay increasedevelop a strategy