I think a concern for the business is whether other people can help maintain the system. As such don’t go too custom and roll your own. Take things like nextcloud and see if you can fit the requirements by bolting on a few docker services. Keep it simple by using “appliances” where it makes sense (dedicated NAS?).
- 0 Posts
- 15 Comments
I lived through those times, this is different. The punishment for false hope is the lesson that things can always get worse.
We’re cooked because our leaders are pumping the AI bubble while crashing the rest of the economy. When that bubble pops those programmers are going to have to find a job in a nuclear sized crater of where the economy used to be.
I am a leaf on the wind, watch how I soar
zbyte64@awful.systemsto Programming@programming.dev•Little frustrated with Github, gpg keys, access tokens and correct setup131·4 months agoThe badge lets others know you’re a masochistic
zbyte64@awful.systemsto Programming@programming.dev•nano-queries - Simple and powerful database-agnostic Query Builder for TypeScript (work with SQLite, Postgres, GraphQL, Redis, PGlite, etc)1·5 months agoThis might be a good fit for a side project I’m cooking up. I am planning on using DBT but I like how this is more dynamic. How does this compare to DBT? Can it turn CTE into views?
Another feature I am hunting for is something that parses the SQL query and produces a pydantic model.
zbyte64@awful.systemsto Programming@programming.dev•Deno v. Oracle: Canceling the JavaScript Trademark172·6 months agoThey just need to delay until the new administration is in place. Oracle’s CEO built the database of new staffers for said administration.
zbyte64@awful.systemsto Open Source@lemmy.ml•The Post Open project asks Open Source developers: would you please fill in a short survey on the current issues of Open Source?1·7 months agoYeah, translating “size of their contribution” to a dollar amount is going to be inherently political. If they’re leaving it open ended to let projects figure it out then that could go poorly…
zbyte64@awful.systemsto Open Source@lemmy.ml•The Post Open project asks Open Source developers: would you please fill in a short survey on the current issues of Open Source?6·7 months agoReading their solutions is interesting; wanted to call out the following because it plays nice if you don’t agree with their whole prescription:
Don’t dilute the Open Source brand. Post-Open will never call itself Open Source, because it has different rules. The Post Open license actually enforces that.
Python Black for Java. Just a thought…
Why make bugs with a better UI?
zbyte64@awful.systemsto Linux@lemmy.ml•Much ado about "nothing" - Xe Iaso (==Goodbye NixOS)1·1 year agoWe don’t see black empowerment in China or a pride parade in Iran.
Sir, this is a Wendy’s.
zbyte64@awful.systemsto Linux@lemmy.ml•Much ado about "nothing" - Xe Iaso (==Goodbye NixOS)113·1 year agoDEI requirements is not nepotism, but let’s take on the core issue I think you brought up: meritocracy. If you show me two people with the same level of skill and experience, I would say the one that came from the most disadvantaged environment is more qualified because they were able to get to the same level with less support.
But you brought in numbers, let me do the same. L Consider that the minority group you mentioned actually has greater barriers to participate, so those 10 people might actually perform better than 80% of the 1000 of the majority group. Assuming both groups have the same distribution of merit is a fallacy.
Regardless of the team size, I say simplify as much as you can so you can dedicate your resources customizing what makes their business special. You mentioned a PBX system and no infrastructure, this makes me think you talking about Customer Management. It sounds like you’re documenting as you go, fantastic. Maybe loop in a noob time to time to review the documentation or have a Q&A that reifies the docs. Best of luck!