Disagree. A ticket should be created for any change, no matter how small. It takes seconds to write a title, body and hit submit. I've seen those small ad-hoc changes cause havoc because someone forgot to escape a single quote or didn't realize tabs were necessary and replaced them with spaces.
The default for Confluence is just that, everyone commits at will. There is no structure, tons of duplication, no standards when it comes to naming, formatting, audience, etc. I'm a huge fan of markdown/plain-text solutions, only because linters can be run that force you down one happy path. I don't believe Confluence has linters at all.
Yep, and that process also involves other people, to review/ approve the fix to the typo.
It then goes from being a few seconds of elapsed time and actual time (to just commit a fix to the typo) to taking hours, days or weeks of elapsed time and hours of actual time and forcing context switching on, and interrupting the workflow of, all of people involved.
You can! At least with GitLab. Our pipelines are written in Python, and generate YAML that kick off child-pipelines. It's fairly trivial and works really well. Having for-loops and building an object based on functions making things so much easier.
You start to wonder thy you have to compile to 'yaml', instead of just having gitlab just give you a normale interface, in the form of a library. And then we've come full-circle.
Nah, Ibuprofen definitely affects the kidneys. It's on my mental list of medications never to try again. It always leaves me writhing in pain (thought it was my lower back that was on fire, turns out it was my kidneys).
Have you ever tried dipyrone? Never had issues with kidneys with Ibuprofen, mostly noticed it with the stomach, but dipyrone was very noticeably affecting my kidneys.
Could not disagree more. For entertainment purposes, I've installed neovim with `brew install neovim`. Opened a small project with `nvim ~/projects/whatever`, and am presented with a screen full of errors (https://imgur.com/D0ydDIG). Pressing enter brings me to a blank screen with even more errors. It then drops me into a vim document with some modal screens and now now I'll probably spend hours researching what all these mean, why this is happening, etc.
All those features you've listed aren't anywhere on the homepage, how does one even do that? I'm interested in learning more, but to think one can do this in a weekend just isn't true.
While I'm sure I could figure out all these kinks, its just software, it's the time sink that makes me pause. I don't see the value here, but I also don't know what all it can do compared to my current workflow with VSCode.
When job hunting, I'll skip those companies that require me to type out my resume. That's why I wrote the resume in the first place. Similar feelings towards those that want it in Microsoft Word format. Companies have their own filtering mechanisms, and so do I.
Hiring in my area, before I retired: (and before everything went online)
They ask for a resume and tell you when to be there.
You show up at the appointed time with the resume. After waiting half an hour. a secretary hands you a generic Office Depot tear-off employment application.
After another forty-five minutes to an hour, you get to see whoever's in charge of hiring. They're looking at the Office Depot sheet, and about half the time they don't even have your resume, which was probably round-filed by the secretary.
The hiring person isn't sure what job you're applying for, so they leave the office to consult with someone else. Twenty minutes later they return and either tell you they're not hiring, or they'll call you next week. (they don't)
My usual response was to send them an invoice for two hours of office workflow consulting at my entirely reasonable rate. None of them ever paid up, of course, but they stole two hours of my time.
Requiring a MS Word format means they're using ATS software. Which parses it and pass/rejects it based on predefined phrases they're looking for. Kinda garbage system.
To me that means their hiring process is extremely formal and not worth my time.
> Similar feelings towards those that want it in Microsoft Word format.
What's wrong with .docx format? You can create it using open source office software. In my experience most forms are smart enough to parse .docx just as well as the obsolete .doc.
Besides, what other formats do you want them to accept? PDF, sure, TXT, sure. It seems silly to avoid word documents.
Word documents are most often required by 3rd party recruiters who want a convenient way to edit your CV before sharing it with an employer. It's not that common but it happens. That's why it's best to use pdf instead. If they insist on a word document, you can just refuse to work with them.
In my experience a lot of time what they want is to redact personal information so they can send your CV to employers without the employers trying to "e-stalk" you and hire you outside of the recruiter (and thus not pay the recruiting fee). I actually got hired like this once (although I didn't know it at the time; the owner mentioned a year after I worked there).
I write my CV in HTML, as that's just the easiest way to get my CV to look exactly how I want it, and then "print" it to a PDF in Firefox. I also have a little JavaScript to redact personal information if I add "#redact" to the URL, and send a PDF of that too to recruiters after I noticed that a recruiter had completely massacred my pixel-perfect CV that I obsessed over by copy/pasting it in some ugly crooked layout and sent that horrible thing to companies :-/
All of that said, I haven't used recruiters for many years, but back then my "redacted" PDF solved the issues for me.
Pasting a picture of each page from a PDF in the Word doc works too, to keep them from editing it. Not sure if there is a way to hide the keywords in it (paste it in white/on/white text, 1-pt font, and have the picture overlay the text?)
My resume is in plain text. I am willing to rename it to have a .docx extension and hope for the best. If that's not good enough, I guess I'm not a fit.
Disagree. The coils on an induction take way longer to heat up than gas, I've gone through that frustration. How can you beat instant fire? The top of it was always scratched which ruined the kitchen aesthetic.
Also, our gas range saved us during the Texas freeze. Used my lighter to get the gas going and we were able to cook and stay warm for a bit, keeping the window open so we wouldn't die. If I'm out camping, sure, pairs well with my portable solar panels and goal zero.
Are you sure that's induction? I think time from hob off to to boiling water on induction is much faster (roughly half) gas. Starts heating pan immediately?
Halogen and resistance hobs are less responsive though.
Am I sure? No, haha. Maybe I don't understand stove terminology. I thought induction were the metal coils that turn red. Maybe induction is different than a regular electric?
>The coils on an induction take way longer to heat up than gas
I think you might be confused about what induction is, might be worth a revisit to know the difference between induction vs a traditional electric cooktop.
I hate PDF's with a passion. Not once have I ever wanted to use one. All the pinching and zooming, such a waste of time. I'm giving this a shot next time I need one, the whole scanner thing needs to go. Are we stuck in the 90's?
Just bought another rental and it was an ordeal trying to find a scanner. Tried the college near me, was denied as you have to be a student. The library is closed down apparently. FedEx didn't have one. The one at the Office Depot was broken. I ended up driving 30 miles to a friends house to use theirs, which required driver upgrades since nobody had used it in a year. I don't understand the point of jumping through all these hoops.
I feel the same with credit card signatures, completely useless and has never once helped me with identity theft or fraudulent transactions. Now I just draw a horizontal line or smiley face.
If you have a basic handle on a GUI Bitmap editor such as Photoshop or GIMP, and you have a hi-resolution phone, you can just take a photo of the sheet as parallel as you can manage and then create a document that is the same dimensions and then use the warp tool to fit the likely skewed photograph to the exact digital document.
ha! As soon as I wrote that I thought "there's an app in that" and started mentally mapping out how it could work. I figured it'd need to be simple as possible, and even considered using the user's location to preëmpt the paper format choice :)
When is the last time you had to pinch and zoom on a website? Text can reflow perfectly well, if you give the renderer the necessary information. With PDF, similar to PNG, you're specifically telling the renderer to put this pixel exactly over there and nowhere else, so it cannot nicely make it all be readable comfortably.
If mobile devices required zooming and panning to read anything, they'd not be popular at all, so they're apparently not where the problem lies.
But then you have super narrow views on desktop, we don't want that either. What's wrong with just using the formats we already have for reflowable text, why bother trying to make PDF into something it's fundamentally made not to do?
Smart phone scanning apps are incredible. I’ve ditched a flatbed years ago and solely rely on my iPhone. It works like magic. The quality is good-to-great, and it fits well with my workflow. Worth the ten bucks or so investment.
Don't even need to spend $10 — the scanning is built into iOS, you can get to it from the Files or the Notes app, or even from your Mac (right-click somewhere and "Import from iPhone or iPad").
I was told by a convenience store clerk that it's best to simply write "SEE ID" in place of a credit card signature. In the event the card is stolen, or there is some doubt as to its user, perhaps the criminal would be stupid enough to actually show their ID.
You beat me to it, was going to say the same. It's always a few bad actors that try and hammer our servers, gets annoying real fast. I'd honestly block them and move on, I don't have time to investigate every single request. Now to sue someone? That seems like a waste of everyone's time.
Yes! Was going to say the same. Kubernetes is far easier to learn than some random bespoke setup. After reading the article, it just sounds like they reinvented the wheel but made it AWS specific for some reason.
Was brought on as a consultant years ago and found their bespoke setup of random ec2 instances and lambda scripts to be far more difficult to understand than just spinning up a managed Kubernetes cluster and having a generic interface to deploy the application, as well as monitoring, logging, metrics, etc.
> Kubernetes is far easier to learn than some random bespoke setup
This, to me, is the biggest advantage of kubernetes. Yes, you can do all the things yourself, with your own custom solution that does everything you need to do just as well as kubernetes.
What kubernetes gives you is a shared way of doing things. By using a common method, you can easily integrate different services together, as well as onboard new hires easily.
Using something ubiquitous like kubernetes helps both your code onboarding and your people onboarding.
Also not having to debug EC2 lifecycle issues is really nice. And you don't have to deal with all of the garbage of setting up ec2 instances (configuring SSH, process management, configuration management, log exfiltration, monitoring, infra as code, nginx, albs, etc).
In addition to ease, why would I, as a s/w engr, want to invest in learning your weird stack instead of learning or using an equivalent tech stack that is actually marketable? Learning a technology can be a huge investment. Why would I want to invest in a technology with not much future and not much ability to translate into another position should this gig go south.
So, I should be OK to use my most precious asset -- time -- on an investment in a dead-end technology, because that investment could possibly, maybe translate (in some reduced way) to me being able to use a different technology later on that is not a dead-end technology? How about I just invest directly in technologies that have a payback and not try to cram the entirety of all software engineering systems into my brain. I already have an unending amount of things and systems to learn in s/w, why shouldn't I prioritize the learning process towards investments that have the best paybacks.
Kubernetes is literally more complicated than any other similar system in existence. It is so by definition, because it builds in more complexity than any other system has. But it also lacks the features you often need, so you have to learn even more to be able to get it to do what you want. You could write several books on running K8s in production.
I was doing research to move set up some new system into scalable cloud infrastructure. My first option was K8s (EKS) and second was plain ECS+Fargate. Ramping up in K8s was so convoluted and painful that I decided to follow up with ECS. That has been quite straightforward.
My experiences with k8s have led me to never propose k8s in a new project. The k8s instances I have seen were bureaucratic and technical nightmares of unnecessary complexity. It doesn't provide a common ground for deployments because everyone will use and configure it differently.
>It doesn't provide a common ground for deployments because everyone will use and configure it differently.
Helm charts are used by 99% of the open source projects I've seen that run on top of Kubernetes. They are all written in a similar style so transferring settings between them is fairly easy. Helm will even create a barebones chart for you automatically in the common style.
A helm chart is not a complete deployment system, it's just a wrapper around kubectl. Neither provides everything you need to completely manage deploys.
But you can't write books on running Linux in production, or Apache, or Windows, or Oracle, or... since the book shelves are (not literally but metaphorically) too crowded for yet another one on the subject
The default for Confluence is just that, everyone commits at will. There is no structure, tons of duplication, no standards when it comes to naming, formatting, audience, etc. I'm a huge fan of markdown/plain-text solutions, only because linters can be run that force you down one happy path. I don't believe Confluence has linters at all.