I'm hesitant to agree with you because it happens so frequently. I'll admit that I've had my share of receiving newbie bashing.
More often than not, I feel like talking with those folks and explaining to them that they should just ask and not ask if they can ask it seems like they just don't recognize what they're doing. Thus, it's usually good to tell them they don't need to ask and to just ask now and in the future.
Have you considered making the question the first line?
I think I understand your reasoning. If you lead with the question, then write a bunch of stuff. When they finish reading and get to the end, they may have forgotten the initial question. I guess I have found in my professional experience that leading the with question is often more effective when talking to management. They're often quite busy and may skim the email to judge the importance.
I find that when they skim they are very likely to miss the question and I usually have to bug them a couple times. If I lead with the question and make it concise and direct, it is often answered very quickly. ;) Yes, this is filler text to share my opinion.
Yes, and perhaps I did this more when I was working in a big corporation (law/tech). But now that I'm running a startup, most of the time I'm chasing people down it's for business development.
In that context, the recipient doesn't have any need to email me back, and I'm trying to make sure they do. For internal emails, there's already pressure for the recipient to email back sometime-or-other, so it's a different challenge.
What's heavy about any of that? I don't know what Tomcat is, but Docker is just a means of installing and running software in a VM(if host isn't Linux), Java is a perfectly fine language and runtime, and Postgres is a powerful and widely-used database. Any other self-hosted web app would require at least a language runtime and a database.
I currently use taskwarrior and nextcloud to synchronize task states between computers. This web based solution would help get rid of the synchronization part if it replicated enough of taskwarrior's functionality.
What I use most in taskwarrior is creating, starting, stopping and closing tasks under projects, then I use hooks written in python which read the changes from stdin and post the task changes to jira and slack.
So if this project could support web hooks, I could write a glue service for it to call when new tasks are created or states are changed.
In my experience, many tables don't have a userid on the table that would be associated with the user. It would be a table join or two or three away.
So the developer may think it is safe to say select value from stock positions left join account on account.id = stock position.id left join user_accounts on user_accounts.accountid == account.id left join users on user_accounts.userid == user.id where user.id == session.userid.
Safe right? We checked userid. But then clicking on the position to drill in on the position data, they just select * from stock_position where stock_position.id = params.stock_id... there's no "and stock_position.userid" on that table, and the developer might be too lazy to spin up the entire join again especially if you don't need account data for this view. Whoops, suddenly a vulnerable page query.
I imagine there are other ways to screw up. Like insecure cookies, and just checking cookie.userid, ah yes, you're the right user. Whoops, didn't realize cookies could be spoofed.
If the cookie is spoofed and someone got another clients authorization token, then they would get any documents that user was authorized to see anyway.
But you don’t do cookie.userid.
You send the username and password to an authentication service which generates a token with a checksum. The token along with the username and permission is cached in something like Redis.
On each request, middleware gets the user information back using the token.
I'm familiar with that process. I was trying to illustrate a picture of how a poor developer might stumble their way into this situation. It's technically possible to store the userid in the cookie rather than using JWTs, but obviously it's not secure in the slightest.
I'm in CA, single earner family, we don't pay even half of my salary in (property/income/sales) taxes. I'm not sure I agree with your sentiment.
I suppose if you decided to buy a property that was more than you could afford, and you're using credit card debt to buy more than you can afford, then you may have a large tax burden. Those are reckless decisions though.
I prefer to use `ls -lah` which always shows the dot files. It sure would be nice if these were placed in a different folder. Maybe ~/.../ to put all the things. Sure, cat ~/.bash_history would need to be cat ~/.../.bash_history which isn't as convenient.
But, I sure do agree with the frustration. My work machine has nearly a hundred hidden things. My Chrome usually downloads things to ~/Downloads/ but Firefox often likes to store the file in ~ which then is often hard to find when I jump over to a console.
I've made an effort to clean things up. Trying to set firefox to download to the Downloads folder, deleting everything personal out of the home folder. But, of course, then that just goes to prove that I do not have control of my ~ folder. I'm doing everything I can to keep my own stuff out of it. Which is sad.
For example, I often hear that O365 licenses are a bliss compared to complexity of microsoft enterprise licensing, when even ms reps don't agree how much licenses you need.
To be fair, "the licensing isn't completely miserable like their other product" isn't exactly a selling point.
My two cents from what I've seen (note mainly see GSuite sie of things).. You can get much more productivity & actual collaboration with G Suite, dependent on a few factors.
One, there has to be total buy-in @ the executive level because you most likely need to completely re-think how work gets done across every function. Often, we do what we've been doing and don't see the full picture because of that existing perspective.
So that requires a legit G Suite partner to help execute change management as for O365 I imagine. It's not so much a risk unless you do it for the wrong reasons; They've done it enough times to have a proven migration formula. Saving licensing costs for example should be on the bottom of your considerations because that more or less evens out and becomes irrelevant.
