Husband, father, kabab lover, history buff, chess fan and software engineer. Believes creating software must resemble art: intuitive creation and joyful discovery.
Views are my own.
This is quite intriguing. But DHH has left so many details out (at least in that post) as pointed out by @breadsmasher@lemmy.world - it makes it difficult to relate to.
On the other hand, like DHH said, one’s mileage may vary: it’s, in many ways, a case-by-case analysis that companies should do.
I know many businesses shrink the OPs team and hire less experienced OPs people to save $$$. But just to forward those saved $$$ to cloud providers. I can only assume DDH’s team is comprised of a bunch of experienced well-payed OPs people who can pull such feats off.
Nonetheless, looking forward to, hopefully, a follow up post that lays out some more details. Pray share if you come across it 🙏
I’d personally appreciate if you explained the intention behind asking these questions.
Is this for your personal market-awareness? Or is it part of a survey (community or corporate?)
A bit too long for my brain but nonetheless it written in plain English, conveys the message very clearly and is definitely a very good read. Thanks for sharing.
I had so many typos - typed that on my phone 🤦♂️ Glad I was able to communicate in some way 😂
Nice work 👏 I can easily see the usecase even without a giant monorepo: a typical MVC app (eg Django or RoR or Grails) which serves both the backend and frontend can easily see the benefit from this.
When i read the title, my immediate thought was “Mojolicious project renamed? To a name w/ an emoji!?” 😂
We plan to open-source Mojo progressively over time
Yea, right! I can’t believe that there are people who prefer to work on/with a closed source programming language in 2023 (as if it’s the 80’s.)
… can move faster than a community effort, so we will continue to incubate it within Modular until it’s more complete.
Apparently it was “complete” enough to ask the same “community” for feedback.
I genuinely wonder how they managed to convince enthusiasts to give them free feedback/testing (on github/discord) for something they didn’t have access to the source code.
PS: I didn’t downvote. I simply got upset to see this happening in 2023.
I’ve been using sdkman for about a decade now and am totally pleased w/ it. It does a very good job of managing JDK versions for you and much more, eg SBT, Gradle, Scala, Groovy, Leiningen, SpringBoot, …
Now, technically you could use sdkman in your CI/CD pipeline too but I’d find it a strong smell. I’ve always used dedicated images pre-configured for a particular JDK version in the pipeline.
I work primarily on the JVM & the projects (personal/corporate) I work w/ can be summarised as below:
docker-compose.yml
.However one approach that I’ve always been fond of (& apply/advocate wherever I can) is to replace (3) w/ a Makefile
containing a bunch of standard targets shared across all repos, eg test
, integration-test
. Then Makefiles are thinly customised to fit the repo’s particular repo.
This has proven to be very helpful wrt congnitive load (and also CI/CD pipelines): ALL projects, regardless of the toolchain, use the same set of commands, namely
make test
make integration-test
make compose-up
make run
In short (quoting myself here):
Don’t repeat yourself. Make Make make things happen for you!
I forgot to mention that the “artwork” is by yours truly. And yes, a 1st grader would probably have done a better job 😅
Good point! I just replaced my LI profile photo w/ an abstract image 🍻
Since I haven’t heard/read about any bugs, I plan to release v5.0.0 on the 13th (😬)
I’ll keep this post, well, posted 🙂
A house!? That’s nonsense!
I’d like to think about 650-700 ft² 10+ year old condos when I need a good vibe 😂
Recently, I’ve found myself posting more often on Mastodon a Lemmy & blog way less - indeed credits go to Fediverse and the mods for making it a safe and welcoming place ❤
Here’s my latest one: https://www.bahmanm.com/2023/07/firefox-profiles-quickly-replicate-your-settings.html
It’s not self-hosted, rather I’m using Google’s blogspot. I used to host my own website and two dozens of clients’ and friends’ until a few years ago (using Plone and Zope.) But at some point, my priorities changed and I retired my rock-solid installations and switched to blogspot.
I used to be in a relatively similar position years ago so I totally relate to what you’ve got to do on a daily basis.
These are the the titles that come to my mind (leaving ths seniority level up to you):
Bookmarked!
I believe you’re already on the right track.
Your pipeline keeps track of the git commit that resulted in each build/deploy. You can use that (curl
your CI/CD API and feed it into jq
) to check out the build definition file for app
(eg app/build.gradle
) from that particular revision, and simply grep
for lib1
and lib2
. It should technically be possible to do this in a few lines of shell script.
Well said 👏
I bookmarked your reply to come back to it whenever this discussion comes up for me!
First off, I was ready to close the tab at the slightest suggestion of using Velocity as a metric. That didn’t happen 🙂
I like the idea that metrics should be contained and sustainable. Though I don’t agree w/ the suggested metrics.
In general, it seems they are all designed around the process and not the product. In particular, there’s no mention of the “value unlocked” in each sprint: it’s an important one for an Agile team as it holds Product accountable to understanding of what is the $$$ value of the team’s effort.
The suggested set, to my mind, is formed around the idea of a feature factory line and its efficiency (assuming it is measurable.) It leaves out the “meaning” of what the team achieve w/ that efficiency.
My 2 cents.
Good read nonetheless 👍 Got me thinking about this intriguing topic after a few years.