Hey, I'm the person that was responsible for adding object storage to Railway. It was my onboarding project, basically a project I was able to choose myself and implemented in 3 weeks in my 3rd month after joining Railway.
Object Storage is currently in Priority Boarding, our beta program. We can and will definitely do better, document it and add it to the subprocessor list. I'm really sorry about the current lack of it. There was another important project that I had to do between the beta release of buckets and now. I'm oncall this week, but will continue to bring Buckets to GA next week.
So, just to give this context. There's no intentional malevolence or shadiness going on, it's simply because there's 1 engineer (me) working on it, and there's a lot of stuff to prioritize and do.
It's also super important to get user feedback as early as possible. That's why it's a beta release right now, and the beta release is a bit "rushed". The earlier I can get user feedback, the better the GA version will be.
On the "simply a wrapper for wasabi buckets" - yes, we're currently using wasabi under the hood. I can't add physical Object Storage within 3 weeks to all our server locations :D But that's something we'll work towards. I wouldn't say it's "simply" a wrapper, because we're adding substantial value when you use Buckets on Railway: automatic bucket creation for new environments, variable references, credentials as automatic variables, included in your usage limits and alerts, and so on.
Gigs is a telecom as a service. We are building Stripe for SIM cards, providing platforms custom phone & data plans through an easy-to-use API in 200+ countries. We are backed by Gradient Ventures (Google), YC Continuity, and investors behind Stripe, Dropbox, Airbnb, Facebook, Spotify & Plaid.
About the Team: We are building our SaaS Dashboard and consumer-facing web apps. We have a high technical standard to build future-proof maintainable and scalable apps. Collaboration is a core part of our engineering culture. We only build great stuff together as a team.
Stack: Next.js, React, TypeScript, Tailwind CSS, React Query, Monorepo
Note: The title of the job listing on our site is currently "Senior Frontend Engineer", but we're searching for Fullstack Engineers with a focus on React and TypeScript.
Hi Timo, me again :) I ended up applying for the backend position because I didn’t see your last comment. I haven’t received a response (18.02.23), is there a way to check? Thanks!
Hi, I'm not involved in the backend positions, but responses for the backend position can currently take a few weeks, due to internal alignment on current needs for backend candidates. I was informed that you should receive an update latest in a week.
Gigs is a telecom as a service. We are building Stripe for SIM cards, providing platforms custom phone & data plans through an easy-to-use API in 200+ countries.
We are backed by Gradient Ventures (Google), YC Continuity, and investors behind Stripe, Dropbox, Airbnb, Facebook, Spotify & Plaid.
About the Team: We are building our SaaS Dashboard and consumer-facing web apps. We have a high technical standard to build future-proof maintainable and scalable apps. Collaboration is a core part of our engineering culture. We only build great stuff together as a team.
Hi, sorry for the late response. The linked position is for the Fullstack position. We're currently in the process of re-writing this position more clearly as Fullstack position. We're not searching for Frontend-only developers, our Frontend Team is a Fullstack Team (we're called the "App Team").
Thanks for pointing out the salary ranges for Fullstack vs. Backend vs. API. This is indeed not correct and confusing. We value all Engineers on their experience and not on their preferred environment or programming language. I forwarded it!
Depending on the country, the "d" means "diverse". For example in Germany, the General Equal Treatment Act demands that jobs must be advertised in a gender neutral manner.
The interesting and useful part of the conference (to me) was the live video chat and Q/A with the 7 devs after the polished video, which is still going on right now.
It is absolutely not a problem that programming is your passion and also your job. For many people, it's a dream come true.
But don't do work in your free time. Don't fix bugs for your employer, don't learn stuff you need to learn for your employer. Don't give away your time for free. Doing work in your free time will burn you out. Doing the same things you do at work will burn you out – it will take a bit longer, but it will happen.
Many employers discourage working in your free time, just because of that (and because in some countries, they're legally obliged to ensure their employees have some free time).
Instead, do your own thing, develop your own project. Probably you'll create 10 side projects and abandon every single one of them after a few days. Something will stick (finding a side project is a whole other topic). Maybe do some open source contributions. Be passionate about your own project(s). And try something new, something you can't do at work. May it be another framework, language, or just some new fancy libraries. It will broaden your horizon and drastically improve your skills as a software engineer.
You will still think of that annoying bug you couldn't fix that day. Those feelings won't go away, but they will be less and less nagging.
Finally, turn off distractions from work in your free time. Mute your work-related notifications, don't check your work mails, they can wait until monday. Oh, and don't forget to meet your friends, go grab your favorite drink with them.
+1000 on this. When I was younger I would work for my employer on the weekends/late nights to try to get ahead. Did that for so many years. I only gave myself a little bit of free time for myself on the weekend.
I _never_ thought I would burnout. “If you enjoy work, work life balance doesn’t matter” I would think to myself. But the point above about “it will take longer, but it will happen” is absolutely correct.
I am now burned out, 13 years later. I’m now going through the process of changing how I think about work-life-balance.
Find a passion outside of work. Think about something that is meaningful to you or some hobby you want to try.
Plan activities with your friends ahead of time - hikes, going to restaurants, just hanging out. It gives you something to look forward to on the weekends.
> But don't do work in your free time. Don't fix bugs for your employer, don't learn stuff you need to learn for your employer.
What hammered this home for me after years of loving my job and thinking about work outside of work, was how little ROI that investment has actually had, compared to how much value it's added for my employers. Now don't get me wrong, I'm pretty happy with my career progress so far, and my love of my job, and learning outside business hours, is a major part of that.
That said, though, I can learn a lot of the same things while trying to invest the time itself in something of my own, where worst case scenario I get the same learning out of it, my employer and my career both still benefit, and I get to choose the direction myself. There's at least a chance, though, that I could produce some extra income, and maybe even build something sustainable on the side where I can personally see a much higher fraction of the ROI, rather than it disappearing somewhere into the enterprise.
I agree. It took a while before I was able to leave office behind after a long week. And while I still have.. homework of sorts, I now go out of my way to play with things that are not related to my job at all ( just bought pine time dev kit -- this will be fun ).
Object Storage is currently in Priority Boarding, our beta program. We can and will definitely do better, document it and add it to the subprocessor list. I'm really sorry about the current lack of it. There was another important project that I had to do between the beta release of buckets and now. I'm oncall this week, but will continue to bring Buckets to GA next week. So, just to give this context. There's no intentional malevolence or shadiness going on, it's simply because there's 1 engineer (me) working on it, and there's a lot of stuff to prioritize and do.
It's also super important to get user feedback as early as possible. That's why it's a beta release right now, and the beta release is a bit "rushed". The earlier I can get user feedback, the better the GA version will be.
On the "simply a wrapper for wasabi buckets" - yes, we're currently using wasabi under the hood. I can't add physical Object Storage within 3 weeks to all our server locations :D But that's something we'll work towards. I wouldn't say it's "simply" a wrapper, because we're adding substantial value when you use Buckets on Railway: automatic bucket creation for new environments, variable references, credentials as automatic variables, included in your usage limits and alerts, and so on.
I'll do right by you, and by all users.