There are plenty of modern, distributed RDBMSes that make sharding transparent to the user (E.g. cockroachDB, yugabyte, vitess, many cloud offerings, etc.). Most NoSQL databases end up adding transactions because they are important, and thus the scale advantages for NoSQL systems over relational databases are diminishing, if remaining at all.
Git is what happens when a technology is born out of hardcore engineering. Most of the world could greatly benefit from its functionality but it’s too hard for non software-engineers to learn. I hope the next era of version control thinks about the problem from a less technically inclined user’s perspective.
Out of curiosity, does anyone know of any good alternatives that make version control easy? I personally love git, but want to see it’s benefits brought to a wider base of people. Projects like Bit are a step in the right direction.
I’ve always been curious, if you’re working on a really complex system with lots of disparate services (or even if you are using a managed database like Spanner for example), what does your development environment look like? Do you spin up containers for all the services? Run a compatible RDBMS instead of the managed database? All my experience has been with systems that can be set up locally - how do you go about developing/testing/debugging without that?
This is one of those posts where you can really feel the value of senior engineering/previous experience.
I definitely have not approached choosing a new technology with the velocity vs. maintenance trade off, instead just choosing the technology best fit for the job at hand. But when looking at a system holistically, this may not be the best choice. It’ll be good to at least know to consider this in the future (although I’ll admittedly probably still bias towards “fun” technologies).
It was done right before the first Crew Dragon launch. They do such a great job of digging into a company’s history and the business model that powers them.
I’m not arguing you should. But there are undoubtedly some people who would. And a hybrid work environment is detrimental to those who want that in-person experience. There should be opportunities for remote-only/remote-first cultures and in-person only jobs going forward. My argument is that a hybrid model misses the point - you lose almost all the benefits of in-person work in the process.
EDIT: I’m a new employee as well, just so it doesn’t seem like I’m projecting what new employees would want without at least some personal experience
Fair enough. My main work experience is at a smaller startup that has a heavy focus on collaboration so my opinion is biased towards that. In my experience trivial things can be solved with a slack message/call but I greatly prefer in-person interaction for more in-depth debugging, etc. But I understand how that’s not necessarily applicable to all situations.
My main concern, and the reason I posted the above comment, is I think companies may over -correct with hybrid work models. For those that prefer office work a hybrid work model is barely better than a remote-only culture; the office loses its benefits when everyone isn’t there. I’m not arguing these remote-only/remote-first cultures shouldn’t exist - in many cases they provide large advantages - but think there will be a significant desire for office-only environments for those that prefer office work.
People often argue that remote working flexibility is the future, but I think it will be detrimental to both younger employees (losing out on mentorship) and those that do go into an office.
An office is at its most effective when everyone is there to collaborate; it loses most of its benefits when only some people are in person. Because of this I think there will be many companies advertising themselves as office-only as a benefit.
For the past few months I’ve been taking markdown notes which are then transformed into HTML and pushed to an s3 bucket for public viewing. Probably not the best solution within this thread but it costs approximately nothing is a great way to get access to a web-based version of your notes anywhere.
This allows you to throw extra features in the HTML like searching for files and randomly selecting a note for viewing at your leisure.