We take pay cuts to work at a startup in favour of equity, not every startup needs a former FAANG Staff engineer in SF, and the idea is for the money to last about a year. If it’s lasting two, investors will be upset the company is turning into a lifestyle business. Get traction and re-raise.
They made it work with $125k, I don’t understand the push back with 3x as much money.
I’m not sure when the Forestry-GitHub integration came to be but Forestry was launched in 2016 and GitHub Apps was launched in 2017.
Their problem (refined permissions / permission to a single repo) can seemingly be solved by migrating to GitHub Apps but, at the time they launched, there was no way for them to ask for permission to a single repo.
So now there are two problems:
- GitHub Apps is a bit of a mess in terms of user experience from both the product side and user-facing side
- Forestry has probably looked at this problem and said “we will make more money by losing out on customers who don’t sign up due to code access vs spending months refactoring the core concepts of our product”.
Eventually, GitHub will become more strict in OAuth vs GHA and then become more strict with what it allows on its platform (similar to what Google has done with Chrome extensions recently).
But at the end of the day, GitHub probably doesn’t care THAT much. If you don’t agree with the permissions, don’t install the app and/or put pressure on the product to refine their permissions. It’s tough to know the lost revenue due to these issues so give them incentive to change.
You can use polling or sockets when the browser is open; the problem is showing those notifications on the phone's lock screen or when you're in another app.
> We have a lot of upset customers thinking that GitLab self-managed telemetry will be mandatory for Self-Managed GitLab moving forward
It may not be mandatory now but, by agreeing to the new Terms of Service, it can be mandatory at any time in the future without being notified/needing to agree to the change (since it's already in the ToS). This Slack conversation is just as short-sighted as the blog post.
I'm surprised the proposal to allow third-party scripts (something GitLab doesn't control!) to run on customer's closed environments made it out of a 30-minute meeting.
ZenHub is the only project management tool that integrates natively within GitHub’s user interface. No lengthy onboarding. No configuration headaches. No separate logins. Developers stay in an environment they love and Project Managers get total visibility into the development process.
We're looking for a motivated Senior Ruby on Rails Engineer to help us to create the new backend foundation for future ZenHub features and products, scaling it to hundreds of thousands of users and shaping the future of project management for software teams around the world.
The ideal candidate has a great understanding of the ins-and-outs of Ruby on Rails, strives to build solid architectures, write clean code, and collaborates with other engineers to continuously improve all aspects of the development process.
Perfect example is Facebook. You don't have to be on it for them to know your phone number. If 2 of your friends have the "Share your Contacts with Facebook" option turned on, chances are Facebook has your phone number/whatever else your friends store on their friend about you.
Not totally true. I went to school with a lot of Mexicans and they would get verbally upset when I referred to the US as "America". As a Canadian, I could care less but they were very adamant about it.
Man, the HN crowd is always rough but I agree with the whole "look for a job" advice. Maybe just for a little while; it's not that bad, haha. You're only 23 so you have a lot of time to figure things out. Plus, you'll learn a lot from mentors there too.
I didn't find my current job directly through the monthly job post but, over a year ago, I found a link to AngelList and then from there I was able to find my full-time job, junior and all.
- Validation is very slow. It was averaging out to about 5s per submission. This should be able to be done almost instantly on the front-end.
- The email input is validated with the type="email" HTML5 attribute. If you write something that doesn't pass, the notification appears (about) 400px above the form. If you write something that does pass, technically, such as "abc@abc", it is returned, by FormCraft, as invalid.
- It would be nice if the input button was clickable, although I can see that this would be more of a Bootstrap thing.
- I'm not sure how I feel about that Budget sliders reading "0-0" and, once clicked on, reading completely different numbers. If there is a minimum, why not show it?
But the point of mobile-collapsing navigation on mobile devices is for a better user experience. Why would you go out of your way to ignore that right away? And if you really didn't want it, you could always remove those lines of code from your file. Or comment them out so it's there when you revert.
This reminds me of Medium spending months to change the underline beneath a descender: https://medium.design/crafting-link-underlines-on-medium-7c0...