skysight-inc/HackerNews huggingface dataset:
It's so cool to look at that 6502 assembly. I had an atari 400 computer, and I had this cool book that taught assembler for 6502 and I hand compiled my programs into bytes and put them in a data program and I could call them from basic. I had this great book called "De Re Atari". Those were fun times. I was in high school and the future was unlimited!
If you're a company providing expensive computers to white collar workers, you should probably just be giving your people new machines to use while their machines are being repaired anyway. In that scenario, it doesn't really matter if repairs take longer because broken machines need to be shipped to Apple.
It's not my method, I was recalling something I learned elsewhere. I've told lots of people about it, so I recall the points that mattered for telling people. I haven't practiced recalling the study authors and name of the study, so I can't recall that stuff.
You strike me as someone who has thought very deeply about this.

I think of it as being too much context. There is just way too much real-world context for computers to assimilate. We humans might be terrible at understanding things like abstract algebra but evolution has left us with pretty well-optimized systems for understanding social cues, complex behavioral networks, and other nuance of human behavior.

I completely agree with your thesis.
Agreed, the name collision is unfortunate - we actually incorporated before Daydream was announced. If there are real issues / conflicts with the name, we're the smaller guys here (our team is just 4 people), so we'll obviously make the corrections that we need to make over time!

Let me know if my response to the Bigscreen question above is sufficient, or if you have other specific questions about anything. Would be happy to dig deeper into anything. Super excited to share the hard work of our team - we've basically been quietly coding for years now, so this is the first time we really get to talk about what we've been up to.
Agreed. I've found the dealership mechanics to be lobotomized flow-chart followers. If X isn't working, replace part A, if that fails, replace part B, if that fails, replace part C.

Why not just run the necessary tests to determine which part is broken?

Source: exhaust valve spring was broken, and dealership somehow wanted to sell me spark plugs and ignition coils, despite my own notes stating that I've swapped them around but the problem didn't move around.
They are lobbying against the right to repair laws because it will limit what they are able to do from a security standpoint. And, since basically nobody repairs their own machines anyway, it would be a damned shame if 100% of their users lost out on having the best security features possible because 0% of their users want to be able to repair their laptop.
The papers that got accepted aren't "buzzword-soup". They're intelligible and in some cases include plausible methodological data. That's one of the things that's driving me so nuts about the prevailing narrative about this hoax: people think what these people did was "Sokal^2", but really it's log(Sokal).
I wonder how often it is an advantage to not know English. Then you might have less baggage from outside the computer and you might map the token to what it actually does in the system (rather than what the token was aspiring to be). Assuming you can get to that point, of course.
That's a very strong statement.

I have used them and I dont agree with this at all.

I suppose next you're going to say I haven't used them enough?
Have a lot of respect for the finomena guys. If they had survived, they would have been our top competitors.
But why? Most of e.g. a website is the software, not the hardware. Making the hardware cheaper but the software more expensive (e.g. with a DSL) is counterintuitive.
Forgetting what you did two weeks ago is a good thing, it gives you a fresh set of eyes and a more objective view of your own code. If you document the main points of the software while you are writing it then that will save you some agony later on.

Regarding technical interviews, the only thing you can do is pick a few examples that you want to retain and regurgitate as needed. If the interview is getting too focused on implementation details then it may be that they are trying to find a reason to not hire you and they will likely never be satisfied. If you find yourself in that situation again then I recommend slowing the pace of your answers way down so that you have time to think.
A pencil point is a tapering edge, so I'm assuming the author is considering <1mm for "fully capable computer the size of a pencil point" being unreasonable.

Microcontrollers are not a huge amount larger than that any more:

-Cortex-M4f in 1.6x1.6x0.65mm (MAX32660)

-Attiny20UUR in 1.56x1.4mmx0.50mm

Bare dies may be a bit smaller than the above.
Yes, agreed. Combination of determination/persistence, belief/self-confidence that success is possible and thus will to continue even in doubt, intelligence, and also interest/passion in a particular area. Align those things and generally some flavor of success is possible for an individual. But why though? Because in general, your "competition" (that is, other people trying to do that same thing) will often lack that trifecta in some shape or form.

I do agree with others mentioning comparisons about the top 0.01% and top 1% and top 1% versus top 2% and all that. At a certain point of achievement, virtually everyone at that level possesses that trifecta to some degree or another and then, in those cases, often luck and a little happenstance play a big part in which opportunities emerge and create significant value and success for only a small few individuals.
Green Cookie – OTW (Spanish Cover)
I had a candidate once. They were having trouble getting the message body on a 400 level error during the technical interview. They had chosen to solve it in Java. I'm not a Java developer (and I let the candidate know ahead of time and that I could only help with naive suggestions). Their exception message was pretty clear. After they prodded around for a bit getting nowhere, I pointed out the exception message. He ignored my suggestions multiple times (multiple angles of "your exception says blah"). After the interview, I took his solution and fixed it per the exception message. Boom. Worked. After the interview, his feedback to our recruiter was that it was obvious I did not know Java. Some people are bad at reading and listening :(. Also, this was a former Googler. It helped shatter an (unconscious?) bias that somehow Googlers were a breed above the rest.
Microsoft joins LOT Network helping protect developers against patent assertions
> Ala -- the antenna is fine, it's your fault you have bad reception. You are not holding the phone correctly

But it turned out Apple was right about that; the iPhone 4 sold for years after the bumper program ended and with high consumer satisfaction.
What are some alternatives you (or others) would suggest to Jira?

I don't mean that to come across snarky at all; I'm honestly curious what people are using and enjoy.
Yeah that and it's interface feeling so incredibly slow / high latency (on prem and cloud / hosted), it /feels/ like Java.
Usually phone screens only check how well you can code, whereas onsite interviewers dig deeper on your design skills and experience in addition to coding. So it could be that you over-indexed on coding when preparing.
This is great, I've had an idea for a service the lets me pause at a specific point in an article and have it remind me to read it. I very frequently lose the momentum in long articles.

It would be nice if I could set some options, like 1 paragraph (or 2+ if they are shorter).
^ disenfranchised programmer alert

Jira's just a tool, a tool with an API, if it burns you so much then set up an email filter and spend a weekend on some GitHub-workalike wrapper or whatever other tool you believe does a better job. God I hate the damned thing, but placed beside all other similar tools in its class, I'd recommend it any day of the week, including over the joke of a system GitHub supplies - hell the ancient Bugzilla even compares favourably with GitHub.
The story behind Turkish Delight
But that really isn't the problem at hand.

There's a big difference between a real brain perceiving artificial stilumation as if it were authentic sensation, versus a virtual simulation of a sentient entity that only exists as data in motion within a volatile memory store.

It's a far greater deception, for an entire universe of distinct sentient entities to exist as a stream of oscillations in a digital circuit, imagining themselves as mortal flesh, than it is for ten, or a thousand, or one billion fleshy organs to imagine a vicarious life unfolding before them, when they can't even move because they're suspended in brine, hooked up to fluid drips, and stimulated by electrodes.

On the one hand, you have a universe brimming with ephemeral entities that need not live as mortals, and on the other, you have limited fleshy blobs, easily placated by limitless sensation, that would have been miserable fleshy blobs whether they had arms and legs and a face or not.

The individual brain in a vat is better of in the vat, while the simulated universe is utterly tragic and should be destroyed immediately for all the undue suffering it needlessly replicates.

The universe in a VM can never know it's not a faithful replication of a higher genuine reality trying to predict future events by fast forwarding the simulation under an array of probabilities. Mostly because it wouldn't be a useful simulation if it could.

Let's say you can simulate planet earth with 100% fidelity, and you want to know if you should drive to work, or telecommute. So you fire up the simulation, and it shows you a fatal car accident. So you telecommute that day, and work from home. Are you ever going to let the simulated version of yourself learn that it's a simulation?

Nevermind that you could simulate bank robberies until you get away with one, or lotto tickets until you win. The point being that, you'd force your simulated self to look at the simulation that says "drive to work" and then watch what happens, while running it parallel alongside the version that stays home. You run it in fast forward, and 9 out of 10 times a freeway pile up kills you, but you score a million dollar bonus that day, based on an opportunity only available from the office. The saty home version misses out on the bonus that gets snapped up by someone else. You now know that starting the car is 90% dangerous, according to high fidelity simulations that are fully sentient copies of yourself, forbidden from realizing that fact, because their deception is essential to the risks they must verify. How do you know you aren't a deeper layer simulation to a higher version of your true self consulting a virtualized oracle of future events?
How long has your company been using JIRA for?

JIRA has a tendency to.... decay. New ticket types are created with custom fields that aren't ever kept up to date. Everyone starts to choose random entries because they have no choice, and no way to add new ones. Once that starts, things fall into chaos because nobody knows the "right" way to file tickets. Tickets soon become immeasurably immeasurable. Projects become categorized incorrectly on a constant basis. The only people who know how to use JIRA effectively are the ones who know how to ignore all the noise. Once those people leave, you're left with pure, unadulterated chaos.

And then you get people who try to fix it by adding a new ticket type or project group, etc. Rinse, repeat.

If you haven't already, then you should check out JIRA's query language and its API. The query language is... special (and doesn't support wildcards, last I checked). Its API, instead of displaying field names as you see it in their interface, shows "fieldname_21234". No joke. You have to run another api request for all of the field names and associate them yourself. It's painful

To your point - sure, JIRA can be used effectively. Though, any bad tool can be used well if enforced. But that's not what most of us have seen in the wild. JIRA eventually just becomes a behemoth of a tool.
Please pay more attention to what I posted: I never mentioned Israel, and I am not biased against them.

The Gaza/Egypt border only allows people, not goods. Goods need to go through Israel/Gaza borders.

If you disagree with this, go talk to the administrators of those borders or modify the treaties that govern them.

If goods could freely pass back and forth there wouldn't be so many tunnels.
Very informative. Wonder how long it took to get from Greece to India at that time? Remember seeing a reference in a book on influence of the Cynics school on the later Platonic Academy, post Roman conquest, to a letter from one wealthy aristocrats' son to another concerning some 'Grand Tour' where they would travel to India to interact with Brahman intellectuals, then off to Persia to interact with Magi (there was a reference to the Dervish being useless) then back to Greece. Must have been at least a two year excursion.
I have a lot of respect for Pivotal Tracker. It's a really elegant design, it is just missing a good detail view on issues, like GitHub's with history, comments, convenient deep linking, markdown, syntax highlighting, integrations, etc. Trello has a good detailed view for its cards, but not as good as GitHub.
May be that you're being confused by the map projection[0] -- South America is much much closer than Australia, and you can also take a direct flight there.

LHR - Rio: 5,734 mi, and it's a direct flight. 11-12 hours ish in the air.

LHR - Perth: 9,009 mi, and it wasn't possible as a direct flight when the map was made, meaning you'd be doing pretty well to get it done in under 20 hours, assuming Perth is even your best jumping-off point. You're looking at another three hours to get to SYD or MEL.

Once there, there are no shortage of airstrips in central Brazil.

[0] http://www.gcmap.com/mapui?P=GIG-LHR-PER
These videos created by a third party Apple repair shop convinced me to ditch Apple:
https://www.youtube.com/user/rossmanngroup/videos?view=0&sor...

He goes into the poor practices they use in manufacturing in general that literally every other manufacturer gets right. They might use under-sized capacitors to save room on the board. The first "unibody" they advertised had two aluminum parts glued together. Some of their repairs for recall-level issues amounted to burning the board, which masks the problem and kicks the can down the road until your warranty runs out. They actively fight your right to repair.

I like how their products look and work, but they really make unreliable products that look and feel premium with substandard engineering, overcharge, perform shockingly shoddy first party repair and generally try to shift blame to customers.

So, for the engineering, you'd want to get AppleCare.. a very expensive extended warranty, on an already overpriced machine, where they will give you refurbished boards/computers, using their own often highly questionable repair tactics, like placing rubber over things to push it harder onto the board instead of re-soldering, or baking the board to mask problems.
I like servethehome.com as a good place to learn about people running servers in their home (thus the name), but that wasn't the greatest article. Look into their forums for more interesting technical discussion.
In Australia it's outright common to have recycled numbers. I've had a few. My work phone had to be given a new number 3 times in the first 6 months until I had a useable one, because I kept getting random calls at all hours of the day/night looking for people who weren't me. It's mostly for work phones for some reason (I assume they have a higher rotation of useage as employees come and go, and nearly all companies use the same provider, Telstra), but my brother got a number that was someone else's before him too so it does happen privately.

The idea of phone numbers being the prime authenticator is laughable. I'll actively avoid any service who ever does this.
See also https://sandstorm.io/
It’s not that JIRA cannot be decent, but in any enterpriseish environment it ALWAYS turns into a monster.

The Jira environment I’m currently working in, takes 2+ seconds for any interaction to update the interface (that’s the sped up version. People tell me it used to take 20...).

Creating a new ticket displays no less than 150 fields (not all of which are required, thank god).
> Finally, Go doesn't do anything to prevent data races, which are the biggest problem facing concurrent code

I've been working on a
multiprocessing library -- built a wrapper function that makes any function, an atomic operation on the state.

https://zproc.readthedocs.io/en/next/user/atomicity.html

(Since it's protected by the actor model, not locks it's an enforcing mechanism)

Do you think this is a step in the right direction?
At least in part, that's due to servers in DCs not being power managed whatsoever 9 times out of 10
For me this is a huge benefit: the engineering team, product management team, qa team, ux team, etc. can each see the things that are relevant to them in the way that they like while still being able to pass the tasks off to the other teams / track them if they would like. You have to put in work to make each flow work for each customer & make sure that the tags are standardized, but once thats in place its super easy (at least for my team)
How hard is it to switch from sales to marketing?
We also have Drescher's Pascal Logo incoming soon.

Preview: https://github.com/PDP-10/its-vault/blob/master/files/aplogo...
The two... archtypical complaints typically I hear levied against JIRA are typically:

1) It's sometimes a tool for managerial micromanagement, such as the extraction of unreasonably certain estimates as "promises", which can then be adjusted further down by your project managers, which can then be used to pressure devs into crunch or worse, instead of as a means of adjusting expectations.

2) It's an extremely complicated piece of software which you can (read: will) overcustomize into oblivion, confusion, and general busywork. Having grown over the years, it's various complications are also not consistent with each other, so some features don't really work well with others. The antithesis of KISS or YAGNI.

3) Project managers will still ask you about stuff instead of referring to JIRA. What's the point of sending time estimates into the void if they're going to swing by and disrupt your flow to hear those same estimates from you in person anyways?!

#1 gives people a (reasonable) emotional reason to hate JIRA, #2 gives people a (reasonable) rational reason to hate JIRA. #3 probably counts for both. I feel like I'm the weird one out not having come to hate JIRA in my social circles.

Project management is important, but JIRA is just a tool, not project management. Ultimately, that's a communication problem with your stakeholders and the people who get to call the shots. Email, slack, trello boards, even water-cooler chit chat can be better than an over-configured JIRA install in the right hands with the right managers. Get everyone on the same page in terms of tasks and priorities, manage expectations, track progress, avoid last minute surprises...

Something like a Trello board is sometimes popular with the "JIRA is overcomplicated" crowd. I use it for personal projects sometimes. It's OK. I'm OK with JIRA in the right hands too though. You don't have to tweak every single knob and settings. You can practice some self restraint and avoid it nerd sniping you, probably.
Would you be so kind and explain what term "high concurrency levels" implies?

thank you in advance.
Nobody ever got fired for picking Jira
Hashtable in c# with examples
I just spent a day eviscerating my 2012 unibody MacBook Pro to replace its keyboard and battery. It’s a little depressing to think that after over 2 decades of using Apple hardware and software it will probably be the last thing I ever buy from them.
It depends on how Jira is used. In your case it appears that there was just oversight added when there wasn't before, but for many of us we get quizzed daily on whether or not we're logging hours for individual tasks, "burn down" is used as a measure of productivity and there are dozens upon dozens of emails sent out to the point where you can ignore everything and still do okay.

This is excluding Jira's design, which frustratingly makes you click several times to uncover data that should be obvious, and various other minor issues that just create headaches, for example: estimations for individual tasks don't bubble up for stories or epics, so you can have two wildly different sets of data to maintain.

The alternative systems would change depending on what people's issues with Jira are -- i.e are they design-based or ideology-based.
I would say, just because you have 7 years of experience, one is not automatically a senior developer. It could be 1 year's worth of experience 7 times.
I was running an on-prem jira. But I felt like I was doing something completely wrong because it was so unbearably slow. I was slightly embarrassed that it was on me that this was running so slow.

Our team grew to the point where we needed a bigger license, so we just migrated over to Jira Cloud. And it was even slower than the on-prem install.

No "no project management" isn't a better solution. No, I can't name any alternatives off the top of my head that are better than jira. But holy cow, jira is not a good piece of software. It has a lot of great concepts, but it runs like garbage and really isn't THAT fancy for what most people require. Especially for the cost.

It's not good, but it's not exactly a risky move either. "No one ever got fired for choosing IBM."
Can technology make the Herculaneum scrolls legible after 2,000 years? (2015)
I haven't tried it, but I've heard good things about interviewing.io. You do a practice interview with someone for free and they give you feedback.

https://interviewing.io/
Also fosil - fing old sh*t in lycra.
Most languages do that internally. It's not a reason you should learn C in particular while you're trying to get an understanding of heaps and stacks.
My experience is that they can sort of see, the things that are sort of relevant to them.

Jira is the definition of a jack of all trades, but master of none.
Fake scandal? No, that's re-writing history. Obama suggested the IRS target his enemies, mostly conservative groups, and the IRS did exactly that. The only thing fake about it is the news reports calling the scandal "fake."
Having used both HP QC and Microsoft Team Foundation Server (the successor to VSS) for issue tracking, I have to say that Jira is better than TFS is better than QC. The big problem I ran into is that many teams had different fields and TFS and QC showed them all. This is a huge problem when there are well over 100 teams.
Seems like a scam.
Good point. Jira's depth and customizability must be like candy for terrible micromanagers. Kind of like how C++ gets an exaggerated bad rap because it is really attractive to people who like building complicated, baroque systems.
Yep :)

The sad part is... yeah, you're right. It's the best ticketing tool I've used, too.

I'm not sure what the solution is. My naive thought has always been that good management can mitigate most of the need for JIRA - even at large companies. Management like https://en.wikipedia.org/wiki/Kelly_Johnson_(engineer), perhaps.
"Most countries outside of North Americs don't have a single apple store" lol. Rinse out your brain.
Highest bracket for ordinary investment income is 54.1%. 37% federal income, 13.3% state, 3.8% federal net investment.

California uses same tax rate for long term cap gains. So highest long term rate is 37% (20% federal, 13.3% California, 3.8% net investment).

If you sell and keep proceeds of $0 basis stock, you get $0.63 per $1.

If you donate $1 of said stock, you get up to a $0.54 tax deduction.

In this extreme example, there's only a 16% gain by selling vs donating.