YC parted ways with the broader HN community at some ill-defined moment coming up on a decade ago. YC started as an inspiring rejection of credentialism and cronyism and slick people jumping the queue in front of tech-focused problem solvers from diverse backgrounds. The values of HN around curiosity, technical meritococracy, tangible solutions to real pain points in the lives of real people underserved by big money tech establishment dynamics were completely aligned with early YC, they went hand-in-glove.
But it got captured by slick dealmakers who managed to cop the hoodie aesthetic and youthful ambition vibe but were the same born-to-privilege punks that have always ruined everything good in computing eventually. Now its messaging is vibe code and gladhand and suck up to whichever political party won last. Its a more insular, more inbred, less substantial network of the "right" kinds of people than the Ivy League was when it stepped on the scene.
And there's nothing inevitable about it, no "big money always goes to shit" story here: its 4 or 5 key people who abruptly had a serious seat at the table and chose very fucking selfishly.
HN is still here geeking out and being a gem on the internet.
Just want to offer a counterpoint. I took a sabbatical last year after working continuously for nearly nine. I felt I had it, I deserved a break. I just wanted to quit and see what happens. First few weeks were great. I travelled a bit, worked on my personal website, wrote a lot of articles, but gradually I sunk into this loop of doing-nothingness. I started playing video games all day, or surfing the internet. For some people this might not be an issue, but as a person who has always thrived on challenging and creative work, malaise started hitting me very soon.
Despite having all the time in the world, my creative spirit sunk to an all time low. All the wonderful things I had planned were not happening.
I do think it was a great learning experience, but I want to offer some advice. If you're going to take one, here are a few things you should do:
1. Think of at least one major thing you would want to work on. This could be travelling, photography or your side-project. It could just be watching movies, too. I think humans like having a routine and have at least one thing to dedicate themselves to.
2. Don't plan too many things. I wanted to get fit, learn to draw, write, read and in the end, I quickly ended up doing nothing.
3. I think we tend to chalk up lot of mental health issues to our work. I don't deny this could be a possibility, but if your work isn't insanely demanding, you don't need to quit your job to fix those issues.
4. If you're planning to work on your project, you need to ask yourself why you can't do it now. Even with most demanding jobs, dedicating some time to a side pursuit isn't a hard ask.
I do plan to take another one, but instead of quitting when I am frustrated as hell, I will do it when my creative spirit is high, and I am feeling more positive about my life.
No it hasn’t. The current economic turmoil has been caused by companies using the stimulus as something they can blame inflation on when they raise prices even though they’re actually increasing their margins. You can trivially see this by looking at the financial reports of public companies that have raised their prices: If they were raising prices to cover increased costs, their margins wouldn’t change; in reality, lost of companies have taken the opportunity to increase their margins.
The whole “Many Americans got an extra few grand in 2020 and that caused inflation!!!” narrative is as fake as the “Organized shoplifting is causing retailers to lose a huge amount of money!!!” fake story and the “Our cities are burned out hulks because we defunded the police!!!” fake story and the “People aren’t applying for these open jobs because they’re lazy and can get paid to sit around!!!” fake story.
Every one of these stories serves a particular purpose for which it was designed, planted, and amplified by specific groups of people with specific policy objectives.
- "lead to the opposite effect in such a case, namely hiding the fact that they lost the capsule."
If you think about it, the impact's more pervasive and serious than that. Even simply saying, "hey, isn't there a potential issue with this bolt" shifts the appearance of blame on the person who's asking. When something does go wrong, the lawyer-attitude types can point to your words, and say "look: they were aware of possibility X at time Y, and they failed to stop it. They were negligent". "If you raised issue A, why then did you fail to take actions B, C, and D, and document them appropriately? You were negligent". To discuss Issue A is high-friction and risky -- for all values of A.
That's at the core of legal culture: "don't put it in writing"; "don't talk to the opposing counsel"; "don't make public statements unless we vetted them (to be as vague as possible)". Opacity. What aspect of human nature underlies this? It's this: blame is nebulous, and it attaches to whatever's most visible. Guileless honesty is a *hazard* in a culture of suspicion.
Obviously that's the exact opposite of what you want from an engineering culture! You want anyone to be able to raise issues freely, fearlessly.
That's the true cost of a blaming-people culture. You're not merely disincentivizing communication at the very final stage ("cover up the disaster"); you disincentivize all communication about risk, at any time. Anything that places you visibly closer to responsibility is a peril.
I worked at Lattice a few years ago, back when it was under 100 people (probably doxxing myself, but whatever). They did a similar layoff right when covid hit. This definitely seems to be Jack's style, owning his decisions and not doing an HR hit-job. This post will work in his favor, no doubt. Glad to see Lattice prioritizing employees -- big fan of the 100k investment idea.
Seeing a lot of people shitting on the product in this comment forum. Plenty of their products are gimmicks, sure, but their real product is that they have a cult-following from the HR community, and they are better positioned to iterate and compete with more mainstream HR tools if they play their cards right. Lord knows they have way too many sales people (AKA "surplus elites"), and need to focus more on their product if they want to have something HR teams don't just want, but need, especially in this new macroeconomic condition. Hopefully the company can move on from this quickly. I don't think Jack is the kind of person who will fuck this opportunity up.
The job search can be difficult right now. Many companies are still determining if they should continue hiring or stop, sometimes even lay off their staff. As a tech career coach & tech recruiter, I recommend the following:
a)try to remain optimistic and patient, I know this will be the hardest thing, but it will be an essential step forward for you.
b)recruiters don't have all the answers you need because they are also waiting to hear back from many different stakeholders. You need them.
c)make sure your resume is the best resume you have ever written. The competition is high right now. I've written a 12-page resume handbook course with two google doc templates that you can use in under 5 minutes. https://www.careersycoaching.com/product-page just sharing this in case someone needs it. You can use the 20% promo code: Interview
d)connect with recruiters on LinkedIn with companies you'd like to work for. They might advertise a role in the near future. When you are connected with them, it will be easy to share your resume directly with the recruiter. But you got to do the work now. You could write something like Hey x, a friend recommended connecting with you. I've heard great things about your work culture. I would love to connect and stay in touch with you; who knows what the future might bring.
e)rewrite your LinkedIn profile. Once the market picks up again, you want to have an impactful LinkedIn profile that can be found. At the very least, ensure you have the relevant tech keywords somewhere in your profile. Thanks, X
f)you need multiple processes to be successful. I recommend having at least five processes, if possible, to increase your chances.
g)the market is changing. The bar is going up; you need to prepare really well for your interviews. Don't wing it. Prep as much as you can. Practice as much as possible for the coding interviews and do your research online. Many companies have their coding questions on the internet.
Hope this helps, if you want me to share more tips please let me know and I can add a few more things.
Noteable is a collaborative data notebook that enables data-driven teams to use and visualize data, together. We build a collaborative data science platform built on Jupyter notebooks using technology like Kubernetes, CockroachDB, and AWS.
We offer:
- Freedom to work remotely anywhere in the US; we are a remote-only company.
- Competitive compensation, including both salary and stock options.
- Medical, dental, and vision insurance, including a top-tier HSA plan, and FSA plans.
Noteable was founded in 2020 by former Netflix, Amazon, and Apple technology leaders, and our team includes contributors and leaders within the Jupyter and Python communities. We are supported by Wing, Costanoa Ventures, and Bain Capital.
Grit | Senior Software Engineers / ML Engineers | New York, San Francisco, or Remote | Full-time | $150–250k + equity
We’re building software to automatically fix technical debt. We do this by combining expressive static analysis tooling (we’ve built a developer-friendly query language for code) with machine learning to automatically migrate code to new patterns and platforms. We’re still in private beta, but have deployed thousands of successful changes for initial customers and have raised a large seed round from top investors (Founders Fund, 8VC, Abstract Ventures).
We’ve got lots of fun challenges at the intersection of machine learning and programming languages. Our stack is Scala, Rust, TypeScript, Python, and Kubernetes. We’re hiring for both smart generalists and PL/ML experts who are interested in collaborating on problems like automatically inserting new types into codebases and using unit tests for reinforcement learning.
Here are a few reasons you might be interested in applying:
- We work fast and focus on shipping, with a single meeting per week.
- We’re working on the edge of the possible and doing deep technical work in parsers/language design and machine learning. This isn't your average SaaS.
- We mostly work in-person in New York and San Francisco, but remote is also possible for outstanding candidates who have proven success in a remote model.
- I’m personally committed to giving real feedback to everyone who applies.
Other than the fact that it is insanely self-indulgent to brag about leaving all this money behind, but it’s not even true. I left my job to work on my own project/startup for a while and the shine certainly wears off after a while.
Corporate security teams are built on three different traditions:
1. The policy/compliance tradition - the kind of people who looked at PCI-DSS and decided that was what they wanted to devote their life to. The accountants of the tech world. You've got resources and want to roll out U2F? That's not in the policy document, we'd rather spend the resources on this great audit of our suppliers' compliance that I've been planning....
2. The be-lazy-be-popular tradition - for the team that hires a guy to reduce other people's workload, not increase it. Resources to roll out U2F? I won't stop you if you've got the money to spend, but what we've got is probably enough - a lot of companies don't use U2F, you know.
3. The hacker tradition - the kind of people who see every real, exploitable vulnerability they find as proof of their 1337 status. They don't care if a policy document says you should disable paste, that's bad advice, don't do it. Rolling out U2F sounds like a great idea - but a lot of corporate environments will chase these types out, or curb their enthusiasm by ignoring their reports.
Perhaps kirbys-memeteam worked in companies with security teams that tended more towards traditions 1 and 2, while your employer's security team had more of tradition 3?
What we’re doing: We’re building the manufacturing operating system of the future based on modern software architecture and design principles, engineered to create network effects as we grow. The product represents a beautiful, sophisticated, quantum-leap forward for the most important core industry in the world. If you have at least two years of professional experience and are interested in building all parts of modern webapps and accelerating the progress of civilization by enabling the next Industrial Revolution, please reach out.
Where we are: $18 million Series A led by Bessemer closed in July 2021. We have a product. It needs a lot of work. We have customers, most are very happy, some complain. 23 Developers (7 from HN!) --> 30 Developers over the next few months.
How we do it: Empathy > Ego, Autonomy > Spec, Delivering Value > Following Trends, Right Tool > Popular Tool. C# Angular. Maybe some Elixir and Vue
Benefits: Immediate 401(k), with 5% match after 90 days through Vanguard, immediate vesting. Health, dental, and vision benefits, a smattering of other benefits. Unlimited vacation (15 day mandatory minimums). Remote and flexible work.
https://fulcrumpro.com/boost
One thing that people need to be aware of, is that Visa does not get to set all of the rules for chargebacks and disputes. You have dispute/chargeback rights that are secured by federal law. They are not as comprehensive as Visa, but in some ways they can be stronger. The problem is there are very few attorneys who practice in this area. I know, because I’m one of them. But some of these protections have Real teeth.
For example, I recently had a client who had his crypto.com account hacked. That account was tied to his checking account. The hackers debited his checking account, by buying bitcoin, and then transfer it out the bitcoin. My client disputed the charges, and the bank denied all of his disputes.
This was all in the context of a well documented breach of a major telecom company. He had all of the substantiation. It was clear that the bitcoin had gone into a very large wallet for purposes of fraud. Despite all of this, he was denied his dispute.
Long story short, we got his $10,000 back, got him another $5000, and the bank pay my fees. That was all based on federal law, not visa dispute rules. So the good news is that these changes do nothing to diminish those lasting rights under the law. But it should put this issue on your radar. If they are starting here, it won’t be long until they start lobbying Congress to soften the protections in law as well
'systemd-analyze security' is a fine thing, just make sure to use the latest version of systemd because it was really buggy in the past. For example, the version that ships in RHEL 8 is so buggy it's practically useless.
I came up with this for most of my services that do require a JIT compiler (so Java, dotnet, etc):
You might want to throw away InaccessiblePaths if your application calls external binaries. The stuff I typically write shouldn't do it.
Some of these flags are not strictly necessary because they should be enabled by other switches, but I prefer to keep them to make configuration more obvious and to mitigate possible bugs (there were some in the past).
If your application needs to store anything locally, add some combination of these:
and you can read the resulting path in environment variables RUNTIME_DIRECTORY / STATE_DIRECTORY / CACHE_DIRECTORY / LOGS_DIRECTORY / CONFIGURATION_DIRECTORY if your systemd is new enough.
systemd will make sure that your limited user can read and write these paths, including their content.
Add this if your application does not use a JIT compiler:
MemoryDenyWriteExecute=yes
And this to prevent it from listening on wrong ports in an event of misconfiguration.
SocketBindDeny=any
SocketBindAllow=tcp:5000
These firewalling flags can be useful if your service does not do much networking to external APIs:
You see them building a delivery fleet as a moat: I see it as they've burned through literally every logistics broker in the US and now have no other choice. Their modus operandi to date was to put bids out to logistics brokers who would treat Amazon like any other customer and have some routes that were profitable, and some they'd lose money on in order to win the overall business. Amazon would then use that broker for nothing but the loss leader route and hammer it until the broker fired them as a customer. You can only do that to so many brokers before there is literally nobody left willing to do business with you.
Source: my buddy runs a broker business and will not do business with Amazon under any circumstances nor will any of his peers in this market.
YAML is not a programming language, and deployment is not a toy task. You need power.
The result is that ansible has pushed a markup language to its limit, then pushed the templating engine used in it to its limit too. Then used a bunch of duck tape + conventions to glue everything and ended up with 10% of an unclean verbose unexpressive real programming language with ridiculous limited tooling, testability and had to document + support it.
As with most DSL.
For what? For the quest of having something "declarative", and that any language could read.
Well you can have declarative API written in any language, and nobody except ansible ever read playbooks.
In the end, it's just a big weight at the ankle. I never ever used it and though, "damn, what a pleasant tech choice, I'm happy they didn't directly expose the API through Python".
It's the same reason I use "nox" and not "tox", or "doit" and not "make". DSL really seem like a great idea, but they fail most of the time. There is a reason only few of them - like SQL, CSS or regex patterns - became a success. 99% of the time, what you need is a good lib, with a well designed API. For the 0.9% of the time you do need multi-language communication, you may implement RPC. Then, only for the 0.01% case should you really consider a DSL.
But we geek love to create DSL. They are fun to write! They are so elegant in tutorials!
Is Pyinfra doing better? I don't know, but I'm sure to give it a try. I really, really want to leave ansible behind, but fabric 2 is not high level or declarative enough.
They drank of the poisoned chalice of ad money. It is bad enough for most, but terrible for them because ads are worse information and search is about getting great information and making it useful.
If google is to be rescued, it must do so by removing it from ads.
Detecting managerial quality up-front is a rather hard problem. I believe it's mostly rooted in the fact that anything meaningful you do as a manager plays on a long timescale (months & years), so you can't directly verify. And it's sufficiently fuzzy that in a short conversation, managers can lay down enough smoke screen to make it hard to see flaws.
So, what you need is getting some kind of long-term view on that manager. There are a couple of ways:
* If you can get it, data. Retention/Turnover, how well people grow, internal surveys. That's almost exclusively available if you transfer within a company, so limited usefulness.
* References. Find people who worked for that manager and ask them. Even better if it's ex-reports, since they tend to be more frank.
* Are they listening? When you have a conversation with them, are they paying close attention to what you have to say, or are they busy delivering a message? You want listening :)
* Can they communicate clearly? Are they able to express what their team does, and what their main challenges are, in a coherent way? In less than a minute? Communication is a managers main job. If they fail at that, you'll have a horrible time.
* And finally, gut check. How do you feel around that manager? If you're in any way uncomfortable, see it as a warning sign. That doesn't even necessarily reflect on their skill as manager - there are just some people we're feeling good around, and some who make us miserable. Skip the miserable part. (If you have a skilled manager, they can minimize the misery somewhat, but you'll still both be miserable.)
It doesn't match my experience, with a real incident.
I was a dev in a small web company (10 staff), moonlighting as sysadmin. Our webserver had 40 sites on it. It was hit by a not-very-clever zero-day exploit, and most of the websites were now running the attacker's scripts.
It fell to me to sort it out - the rest of the crew were to keep on coding websites. The ISP had cut off the server's outbound email, because it was spewing spam. So I spent about an hour trying to find the malicious scripts, before I realised that I could never be certain that I'd found them all.
You get an impulse to panic when you realise that the company's future (and your job) depends on you not screwing up; and you're facing a problem you've never faced before.
So I commissioned a new machine, and configured it. I started moving sites across from the old machine to the new one. After about three sites, I decided to script the moving work. Cool.
But the sites weren't all the same - some were Drupal (different versions), some were Wordpress, some were custom PHP. It worked for about 30 of the sites, with a lot of per-site manual tinkering.
Note that for the most part, the sites weren't under revision control - there were backups in zip files, from various dates, for some of the sites. And I'd never worked on most of those sites, each of which had its own quirks. So I spent the next week making every site deploy correctly from the RCS.
I then spent about a week getting this automated, so that in a future incident we could get running again quickly. Happily we had a generously-configured Xen server, and I could test the process on VMs.
My colleagues weren't allowed to help out, they were supposed to go on making websites. And I got resistance from my boss, demanding status updates ("are we there yet?")
The happy outcome is that that work became the kernel of a proper CI pipeline, and provoked a fairly deep change in the way the company worked. And by the end, I knew all about every site the company hosted.
We were just a web-shop; most web-shops are (or were) like this. If I was doing routine sysadmin, instead of coding websites, I was watched like a hawk to make sure I wasn't doing anything 'unnecessary'.
This incident gave me the authority to do the sysadmin job properly; and in fact it saved me a lot of sysadmin time - because previously, if a dev wanted a new version of a site deployed, I had to interrupt whatever I was doing to deploy it. With the CI pipeline, provided the site had passed some testing and review stage, it could be deployed to production by the dev himself.
It would have been cool to be able to do recovery drills, rotating roles and so on; but it was enough for my bosses that more than one person knew how to rebuild the server from scratch, and that it could be done in 30 minutes.
Life in a small web-shop could get exciting, occasionally.
Just be glad you didn't have to explain an in joke about ftp sites, the local loopback address, and a troll, in a deposition, under oath, to Scientology lawyers, like Keith Henson did.
Readers of alt.religion.scientology were astonished to notice
a large collection of alleged secret, copyrighted and trade
secret protected documents of the church of scientology posted
anonymously over the weekend of May 5. An expert source known to
Biased Journalism verified the documents as authentic.
[snip--to transcript from a deposition of Keith Henson by the "Church"
of Scientology. Lieberman is their lawyer.]
Lieberman: do you know who Patrick J. Volk is?
Henson: to the best of my knowledge I've never heard of this
person.
Lieberman explains that Volk is apparently communicating from
some educational institution in Pittsburgh. Henson still doesn't
recognize the name. Lieberman hands Henson a document.
From: [email protected] (H Keith Henson)
Newsgroups: alt.religion.scientology
Subject: Re: OT Materials...
Date: 6 Apr 1995 19:35:38 GMT
Parick J Volk ([email protected]) wrote:
: Screw the courts....
: I have an ftp site for all the OT materials...
: ftp:127.0.0.1 /pub/texts/news/alt/religion/scientology
: I don't know how long I'll have it up.
: P J Volk
: (alt.2600 lives! All hail the clams and trolls!)
Great stuff! But don't you expect the 'ho to blow a gasket?
Henson: (cracks up) this is a great troll.
Lieberman: (acidly) you find this amusing?
Henson: yes. It's an in joke.
Lieberman quotes from the Volk post: "screw the courts" and
also says that he has an ftp site for all the OT materials. "Mr. Henson is laughing hysterically about this posting for reasons that I suppose he understands--" Henson offers to explain.
Lieberman: What's an ftp site?
Henson explains that ftp means file transfer protocol. You
can use almost any machine on the Internet to access a file on almost
any other machine, that has been placed in an ftp directory, he says
with relish. [He goes on at length about how this is done.]
Lieberman: Okay. "So when he said 'I have an ftp site for
all the OT materials,' he is saying he has all the OT materials on
a site which people can access." Was Henson aware of Patrick
Volk's ftp site? Does this refresh your recollection? he demands.
Henson: well, you see right after the colon, it says
ftp:127.0.0.1?
Lieberman: yes.
Henson: that's a loopback address.
Lieberman wants to pursue the question of the site with the
OT materials. Was Henson aware of Patrick Volk's ftp site?
Henson: (patiently) It's at 127.0.0.1. This is a loop back
address. This is a troll.
Lieberman: what's a troll?
Henson: it comes from the fishing where you troll a
bait along in the water and a fish will jump and bite the thing,
and the idea of it is that the internet is a very humorous place
and it's especially good to troll people who don't have any sense
of humor at all, and this is a troll because an ftp site of 127.0.0.1
doesn't go anywhere. It loops right back around into your own
machine.
Lieberman [not getting it]: So the idea here was to make the
church think that this person had an ftp site and to take action
against him and, in fact, he didn't have it; is that your point?
Henson: Oh, it's really humorous, and I picked up on it
and instantly added something to extend the troll. Extending the
trolls like this is an art form of the highest order.
Lieberman (acidly): I see. So this is part of your art
form where you say, "don't you expect the 'ho to blow a gasket?"
Henson: yes.
Lieberman (starting to lose his temper): so you do remember
this posting apparently?
Henson (helpfully): I can't remember for certain that I
did this one, and certainly I could not swear to any of the material
on here being letter perfect on it (but he goes on to say that it
is such a good one that he would be happy to take credit for it).
Lieberman: You find this whole thing kind of amusing, don't
you?
Henson: Oh, this is screamingly funny.
Lieberman (no more Mr. Nice Guy): You find it amusing to
make Helena Kobrin and the church go after you or other people for
this sort of thing, whether you have the materials or not; is that
right?
Henson: It's a great game.
Lieberman: It is a great game. You really find it amusing,
don't you?
Henson: It's an extremely amusing thing.
Lieberman: All right. You find it amusing when you receive these letters from Ms. Kobrin, the cease and desist letters? It's part of the game; isn't it? [This goes on for awhile as Lieberman hammers at the point. Henson reiterates that he is amused, and wants to talk about the SP levels.]
Lieberman: You find it an amusing part of the game when you receive these cease and desist letters, right?
Henson: No, no. It's not amusing, it's a major increment in status.
Lieberman: I see. You feel this increases your status, right? On the internet, on a.r.s.
Henson: Yes, absolutely.
Lieberman: All right. And it's all part of this game, right?
Henson: Absolutely.
Lieberman: It's all part of the troll, right?
Henson (waving exhibit): This is a great troll. I mean, anybody in the computer business instantly would have spotted this, ftp:127. In fact, it even says trolls in here (indicating). In fact, this was cross-posted from --
Lieberman has heard more than enough about trolls: "There is no question pending. You can hold your comments."
Lieberman (with an air of getting into the bizarre nature of the situation): why did you think this would cause Ms. Kobrin to blow a gasket?
Henson: this wasn't addressed to Helena. He goes on to explain that the message is a loop back. If it worked at all it would be a loopback to your own machine. If you tried it you'd discover it's a troll. The 127 is the loopback address! It's a joke, but the lawyer isn't getting it.
[The observer notices that the RTC lawyer has connected "the 'ho" with Ms. Kobrin. Evidently the nickname has made transit to the solid world. Ms. Kobrin is stuck with it for life.]
Humans have a larger neocortex compared to other mammals, which gives them more storage, working memory, and computational potential than other animals.
The curses of the human condition are anxiety and regret, the conditions that render people unable to engage in the present moment. The former is characterised as being stuck in the future psychologically, and the latter is being stuck in the past. Since neither the future or the past can be changed by obsessive thoughts in the present, these psychological conditions are a recipe for unhappiness, because happiness can only ever happen in the present moment, which is lost.
What characterises flow state and mindfulness is total absorption in the present moment.
What if animals that are not burdened by human quantities of neocortex, such as insects and canines, which exist in the present moment, are actually experiencing flow and mindfulness?
The spider weaves its web in perfect concentration, not stopping to contemplate, plan, or exercise executive judgement. Might not that be akin to flow?
The dog and the cat and the cow and the horse, given physical comfort, do not seem to worry about the future or regret the past. Might they not be blessed with a form of mindfulness that humans in the rat race rarely manage to experience?
HIFI Labs | Frontend / Fullstack Developer with an interest for UX and design | San Francisco, CA (US) | Remote Only | https://hifilabs.co
HIFI Labs is a multi-faceted VC-backed music startup based in San Francisco, with founders who have worked hands-on within the music industry for decades, now taking aim at narrowing the gap between artists and tech.
HIFI Labs is focused on
* Invest in artists at early/mid/late stages
* Grow artists and labels through unique tech-driven, artist-by-artist, kind of experiences
* implement and release in-house products to level-up musicians all over the world
Super proud to say we hosted a multi-platform music festival 3 weeks ago hosted on Twitch, Minecraft and Gather.town. It ended up being the most streamed music-event internationally that week. So much fun! :) (https://friendfe.st)
Tech stack: It depends on the project but recent projects have been a mix of
* React
* React Native
* CSS-in-JS
* Three.js
* Next.js
* Gatsby.js
* Netlify-CMS
* Netlify
* Firebase
* Cloudflare
* so basically all the fun stuff out there.
If this sounds interesting, feel free to ping me at pierre @ company domain.
T-10 before founder shows up here and says something like, “I’m sorry that you feel this way, I’m going to personally fix this”. That will not go well. After about, say 5/6 hours of “reflection”, “soul searching”, “meditation” - they’ll offer a better non apology. Finally a day later, “we screwed up, we broke your trust and we own it”.
It takes a branch in GitHub and use a config file to bootstrap the application inside a K8's cluster using a "docker in docker" model. If you could describe your infrastructure as a docker-compose.yml then you can launch it as a preview.
I'm not really a marketing person so it never went any further than a proof of concept. However, if someone is interested in working with it then I'm happy to support getting it running.
BenchSci-AI Software | www.benchsci.com/careers | Canada, USA | Remote or Onsite | Full-time permanent | Senior Software Engineers, Managers, Tech Leads in Web Application, Data, Infrastructure, Security & Machine Learning teams | Python, React, GCP, Spark, Beam, PostgreSQL, Kubernetes, Docker | Email: [email protected]
At BenchSci, our aim is to exponentially increase the speed and quality of life-saving research by empowering scientists with advanced biomedical AI to run more successful experiments. Our vision as an organization is to bring medicine to patients 50% faster by 2025. Backed by F-Prime, Inovia, Golden Ventures, and Google’s AI fund, Gradient Ventures, we provide an indispensable tool for more than 41,000 scientists at 15 top 20 pharmaceutical companies and 4,300 leading academic centers. Currently, there are 130 of us, and we are expanding! For more information, please email us at [email protected].
This is not a very good article. Here are some improvements.
1. Runbooks go out of date faster than anything. Therefore it is absolutely crucial to have the whole book on a single page and alerts vector to the proper subsection. Also pepper each section with a good set of keywords. This will allow users and newbies to easily search for procedures or related alerts when links invariably break.
2. Group related alerts ("host xyz down") in a single section with many section titles. One for each possible xyz.
3. Go ahead and put commandline commands in the runbook, in shell-command or code highlighted boxes (NEVER inside sentences). User defined fields should be delineated with $HOST etc (never <host>) and sample values for the vars given beforehand with sample output afterward. Never use a copyable $ to delineate shell commands. This creates the best possible user experience for people reusing your commands by cut and paste so they can more easily change values and so they know what to expect.
4. Link all relevant consoles in very small links (CPU usage in clusters: ym qf ij) including historical links to console views for past problems and how they look.
5. Section templates might look like this:
1.8. Too many cacheservers are down
1.8.1 Definition.
This means that 25% of the hosts
(on average) have been down over
the past 10 minutes
1.8.2 Severity.
Our load balancer will route all requests to surviving hosts and clients will retry on timeout so normally this is not severe (there is only a performance impact). However it could cascade due to RAM exhaustion or a query-of-death or due to a config push of broken software so assess the service right away for these problems.
1.8.2 Remediation
... Rollback or resource scaling or bypassing the cache service on the command line ...
Obviously using a throwaway here. Our board members got it into their heads that successful companies must have an AI "play", so they instructed the CEO to invest about 10% of our development budget on AI.
We are doing absolutely inane projects that have no hope of succeeding.
We serve a niche industry where certified professionals have to do certain tasks personally, instead of being able to delegate to secretaries. Somehow our CEO has been convinced that AI can be trained to do these tasks, at a reliability level not achievable by other humans.
Team motivation is in a weird space: everyone is relaxed because there is no pressure to succeed - we all know the project will fail unless someone develops well-perfoming, human-level AGI before Q4/2020. Lots of long lunches and checking out early in the afternoon.
At the same time, everyone is worried how terrible the fallout is going to be once the project reaches its inevitable conclusion.
Interesting times, but at least we can now tell investors we are a keen company with an AI play up our sleeve!
The entire reason advertising exists is to subvert your conscious assessment of what you need, and when you do buy something you "need", you buy the right brand.
In this article, The Economist covers a study credibly suggesting that a world of free movement would be richer to the tune of $78 trillion a year, suggesting that affected by the competition would do better figuring out how to get a cut of the take.
With these kinds of numbers, immigration by default is the only platform that makes sense. The added economic output could do more than fix the highest budget deficits on record; we could be looking at paying off the national debt, free healthcare, and money left over. You're concerned about negative consequences? We can work something out.
Instead, we fret that this is "bad for local workers", condemning the would-be immigrant and our own nation to linger in mediocrity.
I architected and implemented a true-realtime telemetry pipeline. The requirement was subsecond per-user aggregation and round-trip notification of thresholds exceeded. Took us a couple years, but when Halo 5 launched, we handled 2.5B events/hour without breaking a sweat (AMQP over Websockets). It's since been rolled out to multiple Microsoft 1st-party games.
The round-trip requirement was dropped before we launched, reducing the usage of the technology stack to pure telemetry gathering.
The analysts are all perfectly happy with 5-10 minute delays.
But it got captured by slick dealmakers who managed to cop the hoodie aesthetic and youthful ambition vibe but were the same born-to-privilege punks that have always ruined everything good in computing eventually. Now its messaging is vibe code and gladhand and suck up to whichever political party won last. Its a more insular, more inbred, less substantial network of the "right" kinds of people than the Ivy League was when it stepped on the scene.
And there's nothing inevitable about it, no "big money always goes to shit" story here: its 4 or 5 key people who abruptly had a serious seat at the table and chose very fucking selfishly.
HN is still here geeking out and being a gem on the internet.