I really like these doom ports. As if they've become a standard to learn, try something new and let others test it out.
We had entirely AI generated DOOM and now DOOM for quantum computer. Maybe let's try a Doom in Go which is fully CLI?
:-)
A pity is not libre; if if were I could make a few more levels for it as the Inform6 language it's literally a dumbed down OOP language (except for the non-English/Spanish grammar library methods/commands, the ones made in Inform6 itself) and the objects in the game are
self-explanatory to code. Really simple, even a 10 year old could make a shortish game.
Hey, this is interesting. We've already seen UI/Web Dev as a Service coming up. (Some of them are doing a nice job).
And the idea behind this sounds amazing as well. But I've got a question. In your FAQs, you mentioned that:
> "you may not always have enough work to keep them busy at all times"
Can you elaborate further? Why do you think DevOps people might not be busy most of their time?
> Can you elaborate further? Why do you think DevOps people might not be busy most of their time?
What I've seen few times in smaller companies/dev-shops is they just don't have enough DevOps work to keep one person busy all the time. e.g. They need to setup VCP and few ec2, some buckets, RDS etc. That might be just few days of work. Then nothing for 3 weeks and then maybe they need some other things as they work on other stuff or they got other client later.
Also they might have enough full time work for just 2 months and then nothing. That would be too much hassle to find a contractor etc.
Having said that I don't think clients should pause/resume 5 times a month but it's a way for them not to waste their subscribtion if there is not enough work at once.
I also think I should add third plan for existing customer where I'd just monitor and update their infra for lower fee (without doing new features).
It is an interesting article, and a good question, "What can AI never do?"
There is an ongoing debate on LLMs and Trust, that we should take a look at as well. How much we can trust LLM and the data to make decisions.
:)
There is another interesting thing on YouTube. You will see a page loading bar right below the navbar when you load a page. It goes to 75% quickly and then throttles until the page loads. Making the user feel something is working. I've noticed that behavior a lot of times.
