skysight-inc/HackerNews huggingface dataset:
There are tasks you are experienced with that you can pretty much jump on and just do them, but there's also the other 90%.

What's weirdest about your story is that you were laid off a few weeks into your job. People usually get more time to get the hang of it even if they are senior, so I would mostly assume that it was a cultural fit rather than performance.

Some outsourcing/service (billed by the hour — which explains it for the most part) companies would look for very strict delivery cadence with focus on exactly the process you describe, but you'd be unlikely to have contact with the user in that case (just the customer).

Most importantly, if you ever get fired, be sure to ask for the explanation so you don't end up being baffled.
In my own experience (and opinion), your style of development often results in better quality code, less bugs, and cleaner UX. The tradeoff, as you experienced, is time.

I can also tell you that maximum code quality is not always the priority. This is especially true in games, where you ship and then move onto the next project. Even online games nowadays often shut down after not long, and so they don't need quite as much maintenance as a successful SAAS.

Again in my experience, the super-pro devs I know are particularly good at knowing when to be fast and reckless, and when to be slow and calculating.
You most likely ran into a bad lead. His/her role was to coach & mentor you to help you become a better engineer, not just to draw diagrams on a white board.

"everyone knew how to make software" -> if that was the case, you should have found help and support around you organically.

I hope you're in a better situation now. Don't let this kind of experience hurt your self-esteem. You deserved a better place.
This is something along the line what I say in the Scaling chapter in my book[0]. If your infra is really simple (like a server or two), you can actually recreate it in a different provider and beat any hard to fix issue (whole AWS region going down or this Heroku's databases problem).

Especially with smaller applications, you might be able to beat the provider time to fix the issue, and you never know when it might be critical for you to be able to do that.

My book also contains a Bash script to configure you a PostgreSQL cluster in a few minutes with/without attached storage space, with self-signed SSL, SELinux, and more. Great for simple apps and as a start in learning production PostgreSQL.

[0] https://deploymentfromscratch.com/
[1] https://gist.github.com/strzibny/4f38345317a4d0866a35ede5aba...
That's the theory behind chaos monkeys/simian army.
Since it is pretty well hidden and I only found out about it in a previous HN thread: Besides a free plan and contrary to the mainstream, shodan.io has a pretty attractive one-time payment plan. It is probably not enough if you need it 9 to 5 but perfect for the occasional research.

That being said, there is also censys.io. They also don't advertise it prominently, but with their free Community Plan you can search their database for free and you'll get similar results to the free shodan search.
Locksmiths can and do just ignore the "do not copy". And even if they didn't you could just use a machine, tape over it, grind it off etc.

The point is that a key is only hard to copy for the average person if it is hard to copy for the average locksmith.
Not for patent infringement, but because they think you're planning a robbery, because you're 3-D printing a key that is marketed as something a mall kiosk can't copy.
Doing the work that everyone is telling us that they're doing, but they're actually not? They're just writing, "hacking", sharing about it...
Why not keep the discussion in the one place where it belongs, i.e. on IMDb?
> I'm sure FB is doing their best, though.

Is it though? Their entire business model is like alcohol. The higher the alcohol proof the more money they earn. Their algorithms purposefully makes people have wide swings in emotions to drive engagement in order to generate money. Blaming suicidal thoughts on addicts isn't the solution, lowering the alcohol proof is. You can have freedom of speech without the algorithm purposefully pitting one person with another to drive engagement. Exposing alcohol to teens couldn't be a worse idea.
Nitinol
I would expect µMR to be no different than SMR or subs: not refuelable on-site, they’d be delivered fuelled up would run for 10-30 years, and would be shipped back to factory for either disposal or rebuild at EOL.
"Security" is an easy cop-out to justify lock-in. That people that call themselves technically minded still fall for it is a miracle.

What security scenario would you even use as a basis here? Ridiculous...

Totally not resales negatively affecting Apples turnover.
> I suppose that even if it doesn't work there might be a placebo effect at play.

I mean, it's not hard to believe (hah!) that faith, various belief systems and meditation-like exercises are beneficial for mental health. The alternative is generally "the universe is uncaring and nothing you do matters in the grand scheme of things", which is slightly less uplifting.

Completely agree that any related rhetoric should put one on guard, but "the explanations they provide are wrong" isn't incompatible with "they help you live a better life". Probably not worth becoming a zealot and throwing all your money down a certain drain though.
One can purchase more efficient clothes dryers which use a heat pump.

They use only about half the energy.

If you want one, head to any shop that sells appliances, and search "heat pump". Mine paid for itself within a year. You can also buy one 2nd hand for faster payback.
If someone's able to do some kind of physical attack that involves a cable swap style mitm to mess with the face id system, what stops them from also rebooting your phone once?
Exactly! I think it is q bit over 100 pages (140) but still really short. It was recommended so many times to me so I really wanted to make a short summary.

The thing with separating complainers from customer is a great learning as well. If you just see complainers maybe the problem isn't that important ;)
BTW, "Aborigines" is considered offensive by some.

https://www.amnesty.org/en/latest/campaigns/2015/08/why-sayi...
Majority of users are not in the position to understand what a signature is and whether they should accept it or not.

So everyone will just click "Approve" in order to get their phone back. In which case what is the point of even having trusted signatures at all ?
You’d run the pairing process, which can only be ran by trusted Apple repairmen with special internal tools, or any of the guys in Shenzhen back alleys with the device called JC Programmer.
The principles listed in the article look like general common-sense design principles. I can hardly imagine anyone designing a system without understanding the problem domain first - and likewise, the problem domain usually drives the underlying models (because what else can they be driven by)? I acknowledge that something the design process strays away from the original domain requirements (especially among the less experienced teams), but that usually feels wrong irrespective of the design philosophy. So the definition of DDD seems a bit tautological.

I would appreciate an explanation of what DDD is by counterexample - i.e. what are examples of non-domain driven design process? Especially, examples of successful or mostly successful projects - i.e. where the disconnect from the problem domain does not feel wrong from the start.
Oh wow sounds terrible to lie to a blind person but makes totally sense.
How to get meaning from text with language model BERT
Cool thanks will definitely take a look +1
This one is fun. Maybe one optimisation worth checking is what's possible if you have to stay alphabetical.

E.g. T9 puts 4 letters on '9', presumably a good choice as 'X' and 'Y' are rare. Would it be worth it to shift the 'V' from '8' to '9'. '3' has 'D' and 'E' on the same key, maybe move the 'D' to '2' ?
What benefit do the users get from vendors that resolve their entity from multiple disparate ones?

Is this just to serve more ads?
Terfenol-D
> It seems no cloud service provider these days is able to offer what was considered an industry standard.

I wonder how many services really had 5 nines availability pre-cloud era either. Somehow I feel your view of it being "industry standard" might be slightly rose tinted
Ouch! Crazy ;-)
Unless you live on a very tight power budget (eg. van/boat life off-grid), the power your laptop uses is probably a rounding error with or without power boost.

Besides - power boost only affects usage when actually stressing the CPU, which for most people is rare. Gamers are probably the exception.
PC with fiber should warp less and might be stronger. But I'm not sure if it has the same accuracy or any other downside.
Huygens Optics is an amazing channel!
I travel a lot by motorcycle. You can truly see the difference in driver training between countries. It goes from German to murderous. Unsurprisingly, German driving tests are fairly thorough.
Looks really interesting! Added it to my list, thanks :-)
In case of war the communication is censored.
How did you select the subreddits? Most seem to match. I found that The Last Airbender: The Legend Of Korra has /r/Korra with 1.7k subscribers, but there's also /r/legendofkorra with 200k subscribers and more rewatch threads.

> My regexes grew gnarly from occasional tweaks, so I ripped it all out and changed up my process a bit.

Are you still using regex? There was a thread recently about collecting book recommendations from HN comments [1]. The app creator used deep learning and fine-tuned a BERT model with their own data. The results were impressive and I think it could work with unstructured data like yours too. I don't know what's your stack, but anything with Named Entity Recognition (NER) would be a good start.

I really like the lists you compiled. Bookmarked.

1 - https://news.ycombinator.com/item?id=28595967
Yes me too. It was recommend so often that I thought creating a summary is a good idea ;-)
I'd go further... the average number of direct reports is likely 7-8 people, but as you want to cluster direct report by team/squad to a manager sometimes they are unbalanced as the team/squad size isn't neatly divisible by that.

What you want to do is have the smaller teams/squads be the place where new managers can cut their teeth, and have the larger teams/squads be the home for managers looking to become directors. Assuming your statement about growth startup is correct the manager will eventually manage more people and the directors will have to deal with splitting the team, re-org and potentially then managing managers.

I'd add another thing to all of this: Why have managers?

The answer isn't the reason you think. It's not project planning, co-ordination, etc. Books like "Turn The Ship Around" or "The Effective Engineer" show how engineers can more fully own their role and not need micromanaging, and the benefits of that.

The reason for managers is different: Let's say that every 3 years a person has a life event. A life event is defined as something big, traumatic, emotional... both the ups and the downs: Birth, marriage, divorce, death, home move, home renovation, moving country, etc. In your startup of 10 people 3 such events will happen this year... and as a leader you can get involved and help support people. This leads to better retention, no loss of institutional knowledge, improved morale, improved loyalty (we're all human and when someone looks out for us we look out for them).

What happens when you have 100 people? ~30 such events this year. But each is large, will last many months and need a lot of support. Potentially you're now going to have 20 concurrent life events to manage.

At 500 people? ~160 such events to manage each year.

Managers and the People team aren't critical to your success, but their absence or a poor setup is absolutely going to be a large factor in the demise of your startup. The earlier you can structure the organisation to absorb these life events and really support people, the more likely none of this impacts your startup.

Then... once you have managers in place, great... there's a lot of spare capacity there to do more than just wait for the life events to occur. Now you can look at books like "An Elegant Puzzle - Systems of Engineering Management" and look to be a value-add to your team, supporting your engineers on a daily basis to be happier, healthier, more effective. Managers now can help nurture and grow senior engineers, help juniors find traction within their career, etc.
My experience too. “No silver bullet” is correct. DDD has some value but the cargo culting of it gets pretty ridiculous in some places.
Don't get me wrong, I'm no DDD expert by any stretch.

I think the main topic and real difficultly of DDD is figuring out specifically where and how to separate out different contexts (the so-called 'bounded context' in DDD parlance).

Creating microservices is a good example. Where should the responsibility for a single microservice start and finish? What might the implications for scalability and extensibility be? What does this mean for data storage? What data will be shared or replicated between microservices and how will this be done?

Answering these kinds of questions is hard and has big implications for your teams and for your business.
Why doesn't scam firms with male CEOs get the same treatment as Theranos?
How to grab control: 4 tactics used by UI libraries
You're completely right thats what I say as well.
If you're interested in this topic, read it it is barely 140 pages long.
But I think a summary can be a good intro and a good learning for me as well :-)
A few years ago, I made a web app mainly for iPad. The developer experience was bad. It did require a lot of efforts compared to normal web development and it had stupid bugs that Apple didn't bother to fix. Like the clock and the battery would be displayed above the app area if you rotate the iPad after having started the app.
How about releasing the source? I know you want to sell licenses, but there are plenty of projects nowadays that dual-license so that e.g. commercial users pay, but others can still read/modify/compile the code.

(To be honest I didn't even know you could use GitHub to publicly serve a closed-source project.)
(«last», in the original post, was very probably only about the consumption side and the quoted reply only referred to that attempting an explanation.)

I am not informed about E-ink pigment degradation. It is official though that the dot state switching capability is not infinite: after a number of switches - around 10 million to the specifications read a few years ago - the dot breaks.
On this topic, what happened with https://www.jefftk.com/nextbus/ ? Seems to be a 404 now. Was there a breaking change or disruption in the nextbus API?

I loved its bare-bones UI. It was definitely one of the most usable webapps. I assume its a11y was nearly perfect as well.

If anyone would like to see it, here's an archived snapshot:

https://web.archive.org/web/20170622033104/https://www.jefft...

I also admire https://diskprices.com/ for the same reasons.
Exactly in this case "Mom" just refers to a person who doesn't want to hurt your feelings and just tells you that every idea is awesome ;)
You could put the movie files in different folders. And thus create different libraries inside jellyfin.
a) CSAM detection is already done server-side. Client-side was to increase user privacy.

b) It's only for iCloud Photo Library.

c) You shouldn't use SaaS platforms if you are worried about CSAM detection.

They are required by law to take reasonable efforts to prevent the storage and dissemination of CSAM.
Was a great learning experience for me. Looking back, I would've paid to do the job as well
That would be a massive amount of solar, if a tent AC has 7kw and a standard panel has 180w theoretical output.
Is this your project ? https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...
The straight line from point a -> b can only be drawn backwards, i.e. from hindsight. When you zoom out, we all goes in circle/iteration. It is true that in some domains some engineers might have better insight than their users, but not all domains. It is important to keep the humility or be conscious that there exist an unknown world to us.

If your former team lead went from a -> b with no problem, maybe he is part of the circle. Afterall, when you zoom in the circle close enough, it appears a straight line. Or he could be a visionary, I can't tell.

An organization is like a shark, it needs to move forward. That organization can be an one-man team, where thinking overlaps with doing. In larger org, specialization is inevitable. The "no question ask, get things done" way that your former team lead adopted is desirable to certain degree, some of the time. But it is important to be aware of the duality. "Disagree but commit" is a virtue.

A fish can teach you swim, but it probably doesn't know it is in water
Think about for example a planning component for hospital beds... There are a lot of parts that are really straightforward to implement, but for these planning components it might make more sense to develop an in-house component. (Assuming existing constraint solvers and/or rule engines are not a viable solution for you in this particular scenario.)

If your business is talking about updating/deleting/inserting data, you are not describing the actual reasoning behind the change. For DDD, it makes sense to figure out why exactly you are doing the things you do, and model these explicitly in your systems for those parts that matter.

The stereo-typical example for this is an address change: if you model this as an "AddressUpdated", you might as well use CRUD, as this does not specify the intent of the change.

You could change an address because it contained a typo, but you can also change it because someone moved. These might lead to different outcomes, so in DDD you would typically model these as "AddressTypoCorrected" and "ContactMoved".

There are other fine-grained aspects, for example the need of an identity for an object: physical money is considered a value object (so it has no specific ID per instance) in almost all contexts, unless you are the national bank: all of a sudden the identity (serial number of the bill) does matter, so the same "thing" might have different "models" within different parts of the business.

Other examples might be value objects for specific areas, for example weight. Typically weight starts out as a number, and all of a sudden there might be a need to add a precision, mark it as an estimate, or have it "unknown". In order to avoid if-statements all over the code, you construct a "weight value object" that properly manages all of these peculiarities in a single place (i.e. what's the result of an estimate+undefined etc.)
The queen was also historically not such a very powerful chess piece. The rule that the queen roams freely in all directions on the board was established, in her honour, when Queen Isabella I of Castile reigned.
Show HN: Atomic Game Engine in the Browser
> example you picked has a flaw that nude wife will be fined even if she exposes herself on your property

That's not even true for every jurisdiction in America, let alone the world.

> Police officer will be quite quick to explain her why she should not do this

That's not a flaw in the analogy. The point of the GPs comparison is to pick a similar real life scenario in which the fault is very obvious. The fact that you're able to identify the obviousness of the fault (and suggest the police would too) demonstrates the success of the analogy.
Solar pannels don't work at night and you can't ask the enemy to attack on sunny days.
- no auto sync of content like plex/netflix is the biggest one for me
- if the server isn't accessible, the entire app just doesn't work on android. It would be cool to have your shows on the go
- metadata/initial content library setup took ages (read 10+ hours) for me (12+TB content)
- no live-tv over tvheadend.. but that should be similar to plex

overall, not quite ready, but on it's way
DDD principals should only be applied to reduce complexity. If the problem space is really just crud applications, DDD modeling or engineering is a waste of time and money.

But here’s where you have to be careful. It’s still useful to go through things like Event Storming and modeling domains to understand the problem space before deciding that basic crud is good enough.
Now for a second there I was a bit confused and thought this was about forming your business ideas around the available .com domain names.

My guess was wrong, but I'm still confused what it is about :)
Apple is going to be far more concerned about countries like China, Saudi Arabia etc than the US.

The rule of law is significantly weaker and they have already shown that they will go after even mild dissidents e.g. journalists not just mass-terrorists or other more serious threats.

So sure US may have the keys. But unlikely every country does.
Jellyfin forked from Emby about 2 years ago and are still rewriting the spaghetti code from emby.

You can use hardware decoding for free on jellyfin.
It's open source. Emby is now closed source.
>The NSA doesn't have Apple's private keys.

Are you sure? Last I heard the NSA is in the intelligence gathering business... I absolutely would not put it past them that they acquired those keys somehow.

Even if they do not have the keys, bribing an employee and/or installing your own NSA person as an employee in an Apple-authorized repair shop seems like a rather easy thing to do. Or just backdoor the computer that is used to communicate with apple to perform the re-signing stuff. There are thousands of authorized repair shops around the world and you only need to compromise one (or compromise a few so that any "abnormal patterns of repairs" cannot be easily detected by Apple, if it even audits repair logs for suspicious activity at all).

I am sure the NSA has something figured out by now. And not just them.
Plenty. But in most cases there was luck involved.
I do not know what the author means by productivity. On the surface there is a structure in the thought achieved by versioning the term, but beyond that there is just the chaos of ideas. And I am not sold on redefining the words, please invent new ones if you really have to.
Why should I want to be happy?

A major purpose of happiness is a difficult-to-fake signal to others of an outcome being good for me (rather, of it seeming to me to be good/desirable).

Happiness is what happens when I get what I want. Making happiness into the thing I want is almost completely backwards.
Tree wont' be a good fit for comments because one would want to read content by line/word/etc. while a tree item is presented as a whole thing by the screen reader so it's only good for small textual items.
Just to add to that, high color temperaure is also important.
I wonder if we can go back to that and still compensate artists.

Have a music sharing service accessible via subscription. You can share anything you want including copyrighted music. If someone downloads copyrighted music from you, detected via audio fingerprinting, the service will pay the copyright holder from subscription fees - kind of like how streaming services do it now.

Granted this would require copyright holders to all buy-in but I guess we can just exclude the music of non-cooperating copyright holders from the network, again via fingerprinting, although this “restricted form” of the service will be of lesser value.

Now that I think about it, in a way, I feel YouTube has already taken up this role in the aforementioned restricted form since it publishes everything without seeking anyone’s permission and only removed stuff if there are complains.