405 karma · joined August 30, 2016
you can contact me at email (at) ngelo (dot) xyz
I am convinced that some of the teams there are really trying to angle for releases that ship for PR rather than the feedback. (Although some AWS PMs really are trying despite everything else.)
We are hiring Network Engineers for exactly this reason :')
The downtime you see is our proxy taking time to cutover- however, we have https://docs.railway.app/deploy/healthchecks that will only cutover once we have a 200 from your API. This way we can keep your old deploy live and serving requests if and only if it's live.
Theres more we can do to make it magical, but this should help in the meantime.
At the moment we don't but I spoke to the fmr. Head of Support at Stripe and he told me we should think about our product coverage like an API, some parts of the product (builds for example) should be more critical on response times than others. My main goal this year is to publish an SLA table so that we can work with ever larger customers setting the right expectation.
When I first joined- this is why I would take great pains to respond to everyone extremely quickly. When I realized that was not sustainable, the focus then shifted to really making sure that our users are heard and their concerns are acted upon. Sure first contact SLA of 30 mins is great but- doesn't mean shit if we don't solve your problem.
So I think yes, tooling should be first. I think there is just a way for that tooling to serve the developer, not some OKR.
This is actually the original blogpost that we used to make our first hire!
> You will be working with our existing Support Engineer, Angelo - to build out processes, formalize policies, and build out integrations between systems to make it so that we can track and record issues.
I accidentally left that one open... but the Ashby interface is so confusing I don't know where to toggle the visibility. I will remove that and then wait for our jobs page to rebuild.
I get that Microsoft have to recoup their investment but I really want there to be a bonafide alternative to Mac OS even though there are some Linux Distros that provide a close second. Just with last I heard there was drama with the ElementaryOS team- I don't see much hope on that front anymore.
In the case of Dropbox, I would say HN was directionally correct that the software would be commoditized, but I would say that the avg. commenter then would not be able to predict the IPO.
Anyways, I should stop my homelab hobby even though I find this stuff fun. I might pick this up regardless.
https://frame.work/products/12-gen-intel-upgrade-kit?v=FRUPG... https://mitxpc.com/collections/ultra-small-form-factor/nuc-1...
I am hoping this product really takes off. I do kinda see how this can fit the niche of a social RSS + recommendations.
VW's have always had reliability issues with their radio buttons for some reason. It was common for Mk6 or Mk7 GTIs radio power buttons to suddenly not work after a year or two. I am sure this is what caused the edict from on high to transition to their new disastrous infotainment. The thing is, nearly every company who went all in on touch, always had to backtrack at some point. (Like Honda in 2015)
Friend of mine who used to work as a SWE in an automotive company mentioned that one of the pesky issues when it came to developing a new car was the long pole of waiting on your vendor to give you test units of your interior hardware. I assume the push there is primarily coming from that issue as well as the cost savings they get.
The touch issues don't bother me insofar as how slow nearly all the units and interactions are within the car. Delays of 500ms after interaction are frankly unacceptable when it comes to operating anything at high speeds.
I would hate for the automotive industry to just completely focusing on iPadifing your commute rather than focusing on driver/passenger experience, but I assume thats the direction where we are headed regardless.
Speaking personally, I used to work on a Platform Engineering team for a major multinational that rhymes with ay-do-bay. And their requirements for the workloads that we needed to be built and hosted where very unique because you have teams running completely different languages and toolchains, esp. from acquisitions. I can argue there that the template K8s setups wouldn't work.
In the author's case, the only reason why they feel the way they do is because we finally have some sense of standardization on what Infra looks like for most companies. It's no longer a question for most folks if they should adopt Docker, we have accepted images into our lives. Same for K8s (after a certain point of scale). So uh... yea. Catchy blog title to sell some thin layer on top of K8s in which it doesn't solve the root issue that they are talking about.
I work at Railway and a lot of our younger, international users use Railway from their phones (usually in class) and it's quite impressive. Honestly, such a fan of Repl.it its why I am a customer of their service and this is a step in the right direction for the dream of the universal runtime.
o7
Similar to what other HN commenters mentioned on this and other threads. Offering unrestricted compute online tends to be hard to manage from an abuse perspective.
Aside from that: just here to answer any questions about the product/roadmap. We want your workloads to be successful, on Railway or anywhere else. :)
You might be interested in Railway's CLI deployments: `railway up` from your project root gets ya going.
Angelo here (Support Engineer) from Railway. I was personally responsible for implementing the whole flow to link your account to post a support question. I apologize, I put those limits in place to help fight a recent wave of spam. If you can email me directly: angelo (at) railway (dot) app - I would love to answer any questions you may have.
In the meantime, I will be sure to make things right for your account. For others who might face the same issue as you, I will rectify the issue with the support flow moving forward.
Angelo here, Support Engineer from Railway. I am sorry to see you go from Railway and personally speaking, I wouldn't want my PII floating anywhere I wouldn't want it to be.
If you can email me directly: angelo (at) railway (dot) app with your username from HN with your account email. I would be more than happy to make things right here.
Selfishly speaking, I work at Railway and our community maintains a list of self-hosted apps (we call them starters) that people can deploy to our platform. You can checkout the list of apps here: https://railway.app/starters and we even accept submissions via our GitHub repo: https://github.com/railwayapp/starters (Just reply to me here and we can get it reviewed for ya.)
Steamworks SDK was one of the very first companies to offer that functionality pre-baked into their offering "free" of charge when companies chose to list on Steam. After a while, it became the default over time.
For many game companies, what usually happens is that initial investment is easy to go along with for the start when spinning up their game store (Origin, Bethesda.net) but eventually hard to maintain as it's hard to commit developers to maintain platforms.