I think this is the wrong read on the “threat”. One user going out of their way to spent time writing this post is a canary in the coal mine. Most users never give feedback, they just churn. This is the same reason your toothpaste has a phone number on the back - that one random person who cares deeply calls the number and provides invaluable feedback on the product.
It’s not about the one person, it’s about that person representing tens/hundreds/thousands of customers. This feedback is a gift to a product manager that listens.
Some states in the US have banned cell phones or other devices that can connect to cell networks. In our school district at least can connect is the key. Teachers aren’t going around testing if old iPhones have SIM cards so all iPhones are banned. (To be clear, I don’t except them to do that.)
Seems like a lot of kids would love iPods to listen to music at school like we did when I was in high school.
Thanks for checking it out. The focus of Zudoku is on making it super easy to ship beautiful API documentation. There are tons of alternatives, but we didnt feel like anything out there met our bar in terms of design and ease of use.
Zudoku is also the basis of part of our product (zuplo.com) offering so it is extremely extensible. Our managed, hosted version builds on the extensibility of Zudoku to add additional capabilities like API Key management, analytics, etc. Anyone can use these extensibility points to add their own custom capabilities.
Rate My OpenAPI uses Spectral under the hood for a lot of the checks. This is meant to be a quick (and fun) service to help people improve their API docs. Doing full linting with Spectral is complementary - and more than this tool does.
People don’t build applications on Salesforce because it’s a generic platform, they build on it because they need to integrate with the sales/crm process/data/etc.
Edit: To be clear, I’m not saying your idea isn’t good. There is tons of room for this stuff, but be careful in assuming the reason devs use Salesforce platform is because of the features. It’s usually not.
The last time I went to Woodcraft, the guy there was raving about the CNC and recommended I get one. Hard pass. Woodworking is my escape from computers. I’m sure if you do woodworking for a living a CNC is amazing, but I’ll take the slow path on this.
I really like the mix of drag and drop with the ability to also write code. This is something that I always run into with tools like Zapier - they get me close, but then I need a small amount of customization that isn't built in and then hit a wall. This seems like it might be a nice solution. Congrats on the launch.
From Nate Silver: “This article is full of terrible statistical logic. Yes, it's hard to exactly quantify the risk of a highly deadly nuclear accident. By nature, tail events are rare. There is intrinsically some guesswork. But empirically the chances are very low.
The author also blatantly cheats by counting Fukushima as 3 separate accidents, as though they occurred independently from one another and didn't have a common cause like oh I dunno a magnitude 9 earthquake.“
Do you get unlimited vacation though like Salesforce employees? When I worked there nobody worked those days anyway. Will this really have an impact on when people take time off?
While they don’t specifically say what the “language server” is, if it’s the same protocol that powers VS Code[1], this is a big deal. It potentially means that language owners can build tooling that works across IDEs much more easily. Historically, JetBrains seems to have resisted the idea of a standard language protocol (which makes sense as it comes from Microsoft). My guess is it’s becoming impractical to reimplement every language feature for Typescript, C#, Go, etc. Embracing the standard LSP will mean less time spent on low level features and more time building JetBrains only value add.
I think if somebody gets creative about it some of that cost can be reduced. Likely the big drivers in cost are going to be running utilities to support different uses (kitchens, showers, etc.) Maybe a new type of living space can exist where kitchens are shared? Or where there is a gym with private spa-like shower/changing space on a lower floor. I'm not saying these are good ideas (I certainly wouldn't live in that sort of place now), but maybe somebody can figure it out.
This isn’t unethical. There are entire companies that do exactly this. If done well, this is actually an extremely valuable service. It would be unethical if you are hired as an employee and outsourced your work, but as a contractor this is fair game.
The vast majority of docs.microsoft.com is written in markdown. This project seems be both very easy to contribute as well as produces a great docs site.
Longer term this will also likely accelerate servers running on ARM. Writing software on ARM laptops that are deployed to production servers running on x86 servers will start to cause a host of new challenges. The switch to running ARM in production will have many advantages for developers and will likely be very attractive to cloud providers (AWS, Azure) as the costs of electricity for these servers may be significantly less.
It’s not about the one person, it’s about that person representing tens/hundreds/thousands of customers. This feedback is a gift to a product manager that listens.