Thanks for sharing! This aligns with a workflow I've been converging on incorporating traceability and transparency into LLM-augmented workflows[1]. One of the big benefits I've realized is sharing and committing prompts gives significantly more insight into the original problem set out to be solved by the developer, and then it additionally shows how it morphed over time or what new challenges arose. Cool project!
One thing that I've wondered is why sorbet didn't choose to use the stabby lambda syntax to denote function signatures?
sig ->(_: MyData) { }
def self.example(my_data)
...
end
Obviously this opens up a potential can of worms of a dynamic static type system, but it looks sufficiently close enough to just ruby. My opinion is that sorbet doesn't lean into the weirdness of ruby enough, so while it has the potential to be an amazingly productive tool, this is the same community that (mostly) embraces multiple ways of doing things for aesthetic purposes. For example you could get the default values of the lambda above to determine the types of the args by calling the lambda with dummy values and capturing via binding.
Personally having written ruby/rails/c#/etc and having been on a dev productivity team myself, I say: lean into the weird shit and make a dsl for this since that's what it wants to be anyways. People will always complain, especially with ruby/rails.
Count is like Jupyter, Tableau and Miro combined in one tool. Some of the world's leading data teams use it for everything from iterating data models and performing in-depth analyses to creating process flow maps of their entire business.
We're a small team looking for experienced software engineers who are interested in tackling deep technical challenges in the data analytics space.
For the best possible user experience, we have developed various technologies in-house, including a custom WebGL rendering engine, our own data visualization library, and a reactive SQL/Python notebook and database query framework.
Example projects: accelerating rendering using quadtree tiling, extending interactivity and customizability of visualizations, leveraging LLMs in data exploration, developing serverless frameworks for executing database queries at high concurrency.
Sounds similar to most major world/cultural issues today. You can make the exact same argument about climate change for example.
But at the same time, part of me wants to ask... why is this a problem? Why shouldn't we just use science and technology to fix human problems and remove any unfortunate consequences from society?
What's wrong with a world where anyone can eat as much of anything as they want, do no exercise at all, ignore their dental health and smoke like a chimney, yet still have perfect health without any downsides?
Objectively, it would be a better society, with everyone materially better off and a system that doesn't need anywhere near as many resources to care of its citizens.
I agree with this sentiment. I built and led a "Product Design Team" of about 50, and there were no mockup designers on my team. Either the designers can write some code,, or they can design directly in HTML/CSS. The mockup designers work with the team, and I encourage them to understand the limitations and power of the engineering team. I found that many designers end up short at the "mockups to impress the client" stage and are more artistic than being designers.
Any styles/CSS generated by a visual tool will always be limited to the vicinity of that particular design. But in the real world, the design of an entire website/app/platform should be a cohesive network of patterns and consistencies in the whole ecosystem - this is why understanding and designing in HTML/CSS finally makes more sense.
Yes, the standalone designers will be there, but they will always be disabled and limited unless they, at least, learn how the whole thing fits in, and their designs are just the pieces that fit elsewhere in entirely different ways.
I'm lucky to have been able to play the role of a designer, a developer, and business-sy sales pitching to customers and closing the loop by answering questions from all personas. This also did left me being more of a generalist and not a specialist.
Figma and other tools, however good they become, will always be that prototyping tool for playground before the actual work starts.
There is literally a world of biology (text)books that describe the process of evolution and how life came to be. I would recommend finding a syllabus at a local college for a biology class, getting the textbook second hand and then reading it
[1]https://colinmilhaupt.com/posts/responsible-llm-use/