icons VS Ruby on Rails

Not sure if you already are using, but bootstrap has a lot of readymade icons for a project like this.

Bootstrap Icons

You can take the svg element from here. In the filter section type emoji and choose your desired emoji and copy the HTML. It will look like this

💡 This step is optional, but I wanted to use an icon for the close dialog button, which you'll see in a minute, but if you want to follow along, head to https://icons.getbootstrap.com/ ,scroll all the way down, copy the CDN Link, and paste it in the head of index.html

I wouldn't say it is more or less difficult, it is just a lot of work that somebody or something has to do.

Just to take an example, that Excel clone is going to need a whole lot of icons which have to come from somewhere. If you're not picky about what they look like you can find some icon set like

https://icons.getbootstrap.com/

which I picked for my RSS reader because I am using Bootstrap CSS already which itself is a low-effort choice because I use Reactstrap at work. Somebody pickier could look at free and paid icon sets or hire a graphic designer which would involve a significant amount of talking about how you want it made.

I am mainly a coder but my exact responsibilities have varied a lot from place to place. YOShInOn, my RSS reader and intelligent agent, is a one-man show which eliminates the overhead of communicating about things but means I don't get the benefit of other people's insight. I worked at an academic library where my first assignment was to take a very detailed Photoshop comp and make HTML that looked exactly like it. In other places nobody told me how it was supposed to look, or it was obvious from the get-go that I was supposed to add a new field to this form and it is going to have look like the rest of the form. I worked at a web development company where I worked on about 70 web sites in 8 months and we did projects very fast and cheap and forms that we made from scratch always followed a style guide we called "spider forms" which meant we could get better-than-average results without spending much time thinking. Where I work now I don't make decisions about the database schema except when I do, other places I was basically a DBA.

So the point is a "coder" can have varying levels of responsibility for UX, business rules: they can get very vague descriptions of what it supposed to happen and they figure it out, or I can get very detailed storyboards for everything. One way or another a lot of design and planning work has to get done.

A "low code" or "no code" system, whatever technology it is based on, is going to have to have a lot of decisions already made for you within some particular domain. Most of the worlds' business applications involve filling out forms and updating a database. But you might want a toolkit for making games that look like The Legend of Zelda with very little coding, or maybe something for making applications that put objects into your space with a Hololens or Apple Vision.

You could bust out apps really quickly if you take the defaults in a domain but if you want to make something really special the sky is the limit for the talent involved. Take a look at the credits for a major video game for instance.

Bootstrap Icons are packaged up and published to npm. We only include the processed SVGs in this package—it's up to you and your team to implement. Read our docs for usage instructions.

[0] is a my favorite demonstration of it.

[0]: https://github.com/rails/rails/commit/b83965785db1eec019edf1...

Here's a real life example: Imagine a Ruby on Rails app on which a team of developers are working. The code is hosted on GitLab and all the work is coordinated using GitLab issues. In other words: For every commit, there's an associated issue and the issue number acts as a sort of primary key for documentation, time reporting and so forth. This convention has a few advantages, most notably the ability to easily learn more about how, when and by whom features were implemented as well as how this implementation came to be.

Ruby on Rails is regarded as one of the best ruby frameworks. It was the primary language in developing big projects such as Twitter and helped the language boost the community. Often referred to as “Rails,” Ruby on Rails is a web development framework with an MVC control structure and currently running its 6.1 version. The 16-year-old language has dramatically influenced the web development structures and managing databases, web pages, and other components on a web application.

In Rails 7.1, a new option _instance_methods is introduced, allowing developers to opt-out of the automatic generation of instance methods for enums. When enum is defined with _instance_methods: false, Rails will no longer generate methods like pending?, processed?, etc.

Rails isn't super opinionated about database writes, its mostly left up to developers to discover that for relational DBs you do not want to be doing a bunch of small writes all at once.

That said it specifically has tools to address this that started appearing a few years ago https://github.com/rails/rails/pull/35077

The way my team handles it is to stick Kafka in between whats generating the records (for us, a bunch of web scraping workers) and and a consumer that pulls off the Kafka queue and runs an insert when its internal buffer reaches around 50k rows.

Rails is also looking to add some more direct background type work with https://github.com/basecamp/solid_queue but this is still very new - most larger Rails shops are going to be running a second system and a gem called Sidekiq that pulls jobs out of Redis.

I'm looking forward to see what extractions from this will land on rails. For example: https://github.com/rails/rails/issues/50454

Here is what strict_loading does (source):

Kamal is a wonderfully simple way to deploy your applications anywhere. It will also be included by default in Rails 8. Kamal is trivial, but I don’t recommend using it on your development machine.

Here's the GitHub milestone I've based this article on — https://github.com/rails/rails/milestone/87