@lorentz well yes, that's also not that hard to find indeed. But none really mention _how_ to do it _without_ enabling the firewall rules which then block you out (i.e. using the offline variants).
But what nobody mentions either is the fact that (at least in my install) port 22 is open by default to prevent this either way hahaha

Good thing you kept a healthy git history of all your changes so you can at least recover most of it, right? Right? :(
Hopefully you don't need to start from scratch, that sucks

But hey, at least it seems like you can easily outperform them both in practice as well as in theory ;)

Damn how did this get published... Everything I read here is bloated crap where they tried to use the most fancy and longest sentences to say nothing worthwhile. Instead of describing what a feast the background research was, why not simply write down your findings of the background research? Worst of all: why do they even write about what a research question and hypothesis are? EVERYONE in academia knows what those things are and you simply write them down and get on with your paper.

It's like they had one week to and we're forced to use at least x words or something childish like that...

Sounds to me like your ceo should be busy with hiring product owners who actually do know how to manage technical projects instead of comparing actual human beings with a text generator. I'd be offended by it if it were me to be honest.

For what it's worth: not receiving actual requirements/expectations is the best way to get in a endless cycle of bullshit rewriting/expanding because nobody knows what they want/need and nobody knows what to expect from you. Please try and get SOMETHING out of it for your own sake or otherwise at least suggest a list of possible improvements to get some expectation management in place.
If you don't scope things down you'll soon have issues which would've been easily prevented by this and then it'll be on you because of course it's never the lack of leadership/portfolio management...

Yeah I really like documenting the actual links instead of simply describing how to get there or hoping to memorize it.

Im actually planning on trying runme somewhere in the future for interactive readmes, which provides a bash kernel to markdown files. For your use case it would then make sense to use their cloud integrations as well I guess.

Looks like a really neat tool to both enhance the efficiency/workflow and make markdown files unnecessarily complex

Being able to undo almost everything you fuck up IF you don't do bat-shit crazy stuff. Even better if it's in a container you can simply redeploy!
Main hold-back on fixing/doing stuff in the house is me getting anxious I fuck my wall up or hit some pipe or smth...

Best of luck, hopefully it's benign!!

Always sad to see useless logging: half our issues can be either prevented or fixed by having clear logs...

@devRancid long story short: they store all auditing logs on their side for free (as in free for them), but we have to pay to store those same logs for production troubleshooting and account monitoring.

Its like the most profitable scheme in IT I've seen as of yet.

@jestdotty I hope it's your experience that changed at the very least ;p
But yeah, you can be "functional" for menial stuff like coding but that does not mean you are actually optimally functional where it counts, especially regarding motoric handling, reasoning (@kiki's points), and reaction time for example.

@Lensflare sounds good! Hopefully it works out as you intended!

So it's kinda like RobotWar and all its clones? But sounds good, curious how you envision it being unique :)
I also remember having played some game for my study where you program "bots" which can also infect others and inject their code into other bits which was awesome

But sad, I drank more than 3 :(

@jestdotty getting used to a state does not mean you are not "in" that state FYI, it's just an excuse to keep taking in more...
There are so many people who drive under influence (over the legal limit) with their excuse being "I feel fine, I only had x glasses" while all they do is basically admit they have a problem and unnecessarily bring other people in danger

@jestdotty oooh I like the idea of splitting the front end, especially since managers and POs simply have different workflows/use cases than the people who are actually working on/refining the tickets.

- It's intended to be easy to use for EVERYONE and be used for ANY methodology, making its workflow cumbersome
- It's developed by Atlassian, who don't give a fuck about important/useful feature requests or making your life easier. Force you to use paid plugins
- Any somewhat advanced Jira JQL/automation is only possible through paid plugins
- The jira admins I've experienced are either completely unaware of the wishes of the actual daily users or simply do not understand how you can get the most out of it
- It gives developers yet another application we need to use while all major CI/CD providers provide the same required functionalities in a simpler workflow with way better integration

Look, I like the idea of Jira, but admins rarely allow you to use any automation and/or plugins to actually get something valuable out of it and instead try to make the ticket flow inefficient. And I want to pair my goddamn tickets to git branches which nobody ever implements in the team workflows :(

@Demolishun yeah thanks, I hate it...

@kiki glad to hear, keep it up! You deserved the praise

You did awesome last year, now you can continue your streak of "best year ever" (no pressure ;) )!!
Trinity will definitely help you with that

@joewilliams007 that entire "new" teams experience is horrible imo. Want colours? Use these weird words which kind of relate to the basic colorset instead of just using their names. And for extra good user experience they removed the colour preview as well.
Want to add a subtitle to your basic chat message once in your lifetime? They got you covered with a by-default subtitle feature which you have to click out of explicitly.

That's not fun :(

In before the coworker then quickly invites you for a last-minute meeting because you already had that time reserved, so it's perfect timing right?

Companies are a whole different story I think, because they need to appoint valuable resources to even try and get you up and running. So those might need some extra convincing...

It's really simple to start searching for one actually: I searched on the university's and any attached institution's websites for interesting departments which already had upper-year internship vacancies and simply sent an email to the lead professors asking if they happened to need someone with interests x and skills y.
I sent 3 emails, spent some time with 2 departments, and ended up in France for five weeks assisting quite some niche research. Free travel, all-inclusive stay in the professor's farm together with the team, and nice sightseeing.
Don't expect anything in return except for a good resume entry/experience doing something you are actually interested in: if there's one thing that professors like, it's free/cheap enthousiastic labor!

Not really a code freeze period, but at my current project they use locked dependency files which can very easily refer to 2-year old custom packages if the importing package is not updated regularly.
Ir drives me mad when a 2-line code change results in 3+ packages LCM work with debugging and fixing errors in UT and sometimes E2E...
So for the love of god: if you have any influence in how your pipelines run and how your codebase is managed, try and get some weekly build/deploy (depending on your release intervals) which updates and tests EVERYTHING

I couldn't imagine having to work with code freeze periods o.o

Wait, where is Red Dwarf?! O.o

For me, it all boils down to having to alt-tab between windows when a split-screen setup is not sufficient. No way am I going to alt-tab between windows every few minutes.
For me it saves time, prevents context/focus switching, and makes me more efficient in everything I do.

Need to write docs? Open two full-screen windows: one for code and one for docs. Code can be split into more boxes when you have different contexts.

Need to debug? You'll definitely need a full screen window for stack tracing and more, depending on what languages/tech you work in.

Have a meeting or need to present/demo something? Use your second screen to keep an eye on the chat and the cameras while shared content is on your main.

Experimenting with new packages/functions or simply having issues with third-party packages?
Open their official docs/etc in a Web browser on one monitor and have your IDE open in a second one.

Visualizing/tidying data? Have your scripts on main and visuals/tables on the second.

That's not a "women" thing but a simple fight or flight reaction mate. You could also try supporting her instead of making a fool out of her in a rant and projecting it on all women while it could happen to anyone. It sounds like she didn't really want to go but caved under social pressure.
But no, it's not really smart to take on a job where you know for 100% that it will happen someday..

@dissolvedgirl all the administration aside: if they're not prepared to pay a very small fee for a multi-region hosted static webapp, then they can't complain about the downtime.
If it's critical to have x% uptime, pay for guaranteed x% uptime