memes

10149 readers

3014 users here now

Community rules

1. Be civil

No trolling, bigotry or other insulting / annoying behaviour

2. No politics

This is non-politics community. For political memes please go to [email protected]

3. No recent reposts

Check for reposts when posting a meme, you can only repost after 1 month

4. No bots

No bots without the express approval of the mods or the admins

5. No Spam/Ads

No advertisements or spam. This is an instance rule and the only way to live.

Sister communities

[email protected] : Star Trek memes, chat and shitposts
[email protected] : Lemmy Shitposts, anything and everything goes.
[email protected] : Linux themed memes
[email protected] : for those who love comic stories.

founded 1 year ago

MODERATORS

Tenthrow

The_Picard_Maneuver

[email protected]

512

I swear it slows down when it knows I'm in a rush. (lemmy.world)

submitted 4 months ago by The_Picard_Maneuver to c/memes

48 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Valmond 3 points 4 months ago (1 children)

When you have a nice setup in programming (compiler, database, diverse docs, shells etc), you don't want to shut all that down. If you can, good for you!

[–] [email protected] 3 points 4 months ago (1 children)

My dev VM is almost entirely disposable. Could be up and running again, fresh in 30-60min, not counting time to pull the repo. Why use a local db server? Seems weird to me but, I came to development through SysAdmin and support stuff, so, was used to not owning the machine that I was on. That probably has heavily influenced my workflow.

Out of curiosity, would you mind sharing a bit any the languages/frameworks and workflows that you are using? I'm mainly using Go, C++, Python, and a few others and just having trouble figuring out how I'd arrive at a situation like that. No CI/CD and test systems?

[–] Valmond 3 points 4 months ago

Well if I shut down visual studio, it takes some time to relaunch it, it uses a distant unix server to compile.

I usually have a bunch of explorers open on distant repos for checking traces. Some soft connected to a database (with tables open), shells open on servers, or inside a docker on that server, all that goes away at reboot.

Nothing crazy, it's just convenient to just continue working instead of having to set it all up in the morning.

CI/CD, thats for integration and should IMO be on a server somewhere 😁 not on your PC that you shut off in the evening!

I do mostly C/C++, linux/windows. Database, gui, etc.