HN user
I keep the in-extinguishable fire under bay.
Been there done that - SRE/DevOps/SecEng/SysEng/SoftEng
[ ... ] if you're clueless.
Done it. Therefore, I flex. I was talking about clueless folks like yourself.
Again everything you've said does not really apply here or is impractical.
YMMV. Always.
wtf are you allowing plex to initiate outbound connections to begin with?
and why is plex not in it's own VLAN with a egress FW rules to second with?
lastly, why aren't you running snort/suricata to inspect the packets originating at plex?
let me solve this problem for you - it probably doesn't bother you at all.
otherwise, you'd scratched your itch a long time ago.
Clueless lol.
It's ok to be clueless. And, it's ok to be working for a FAANG and be clueless too.
Rockchip calendars
.< haha i remember this
Haha made my day
MM is basically up-selling his _Signal_ trust score. Granted, Signal/RedPhone predecessor upped the game but calling this E2E encrypted AI chat is a bit of a stretch..
Go read a book on basic cryptography. Please.
I'm a Tech Lead, and nobody listens to me. What should I do?
TL;DidntRead
Precisely. Take the `TL` title out the door. Take the `ego` out the door.
Then, step in the door - as a friend, with empathy, proactive listening and support the engineers.
Round-table `discussions`. Not Waterfall.
My 2 cents.
The people configuring WAF rules at CDNs tend to do a poor job understanding sites and services that discuss technical content. It's not just Cloudflare, Akamai has the same problem.
I agree. There is a business opportunity here. Right in the middle of your sentences.
Hint: Context-Aware WAF.
Many platforms have emerged in the last decade - some called it smart WAF, some called it nextgen WAF.. All vaporware garbage that consumes tons and tons of system resource and still manages to do a shit job of _actually_ WAF'ing web requests.
To be truly context-aware, you need to compute a priori about the situation - the user, the page, the interactions etc.
Thank you.
<3
<3
Bottom line is: GitOps means the source of truth is Git and automation makes sure to avoid drifts. You still have to have a rollout strategy and schedule that makes sense for your usecase.
THIS.
Thanks! This is great. If you ever need extra housing for this, I would be glad to provide it.
I couldn't have written it better than Phil. I think it is important to take some time out for yourself.
I feel for you.
What do you truly truly enjoy?
It's easy for me to ask you question.
Often times, the answer lies within.
PS: Please enjoy the time with your child; It doesn't come often in a life time :)
beep! Official GUI client missing for Linux.
This post feels especially jaded and anti-intellectual. Writing simple code isn’t stupid, why be so harsh on yourself?
The reason I think self-critique takes a rather extreme turn is because of anxiety. If we analyse the root cause, there may be more than _just_ anxiety at play but I do feel it plays a significant role(IANAD though; just an observer).
Every programmer first and foremost are humans. And as humans, we are bounded by the highs and lows of the software we develop. Some of the low self-esteem can come because _life_; some might be because they hold their bar too high to achieve dramatically; some because, they might think of engineering software as an easy-peasy task but find that it can _sometime_ come with unseen/unheard baggages; all or partial part of the aforementioned causes could lead further to be in said state of mind.
To some extent, we(as in software people) need to be brave, hold our self beliefs/values, try to elevate our self-esteem and recommend our friends/family/colleagues to do the same. It's this collective esteem that will carry us together in this journey. It's not easy to overcome fear, anxiety, depression or any other state of mind(IANAD though; just an observer). I am cognisant of the fact that it is definitely easier said than done but do note that humans are capable of achieving marvelous things both intellectually and viscerally.
Perhaps, try to be social, go out and about, have hobbies, meditation, hiking, exercise - just to name a few that helped others I have met.
Last but not the least, I cannot let myself buy the argument that someone thinks of themselves as dumb. It's extremely more likely that one has not had the opportunity to have the __foundational__ understanding and the shift required to think laterally in those terms. To acquire those, perhaps try to read more books and experiment more. These are more valuable use of time IMHO than to be harsh on oneself. But, to re-iterate, we are all humans at the end of the day.
https://github.com/microsoft/QuantumKatas (this one can be run locally for learning purposes using Jupter notebooks)
Whilst being Microsoft platform, still the katas are great https://quantum.microsoft.com/en-us/experience/quantum-katas
If you want go deep, you will need to refresh/learn few key mathematical foundations that form the basis of QC. They are definitely not hard IMHO. If so, then read Michael Nielsen and Isaac Chuang excellent book https://en.wikipedia.org/wiki/Quantum_Computation_and_Quantu...
Hmm. There are "plenty" of Rust jobs outside of crypto stuff. They are:
- Your typical service driven stuff (aka full-stack/backend/microservice et. al)
- Tons and tons of opensource projects from AWS (investing), Microsoft (investing) and Google (yes, investing) to name a few off the top of my head.
- Startups have so to speak started embracing Rust https://corrode.dev/podcast/
- Embedded Systems <- C/C++/ASM's bread and butter traditionally.
- Rust ecosystem is maturing faster than anything I have seen in the past (ok, maybe Go's ecosystem was fast as well).
Regarding AI and ML stuffs: While I do agree that chasing such hype may be intangible in the very short to short time frame. No doubt, the AI winter may follow a typical curve and follow up with a AI "summer". _Every_ major technology in the past 20-30 years has followed a V curve. AI/ML probably won't be an exception.
I understand that the OP may have hobbies outside of "learning" but making a dedicated time outside of it will yield by leaps and bounds. Always be learning (make time for it) - that's the gist in short without going into the nitty gritties.
Nice. I don't have anything for you but maybe this will be useful:
My two cents: o Learn machine learning, artificial intelligence - fast.ai
o Learn Rust, Rust, Rust and some Go
o Scala is good. Keep it. All the stuff you learnt whilst using Scala and Python will be useful in _Rust_.
o SDE is huge. Try something other can webdev and gamedev.
No matter what others may say next frontier will be roughly these: - Artifical Intelligence - Quantum Computing
Get good at these. Now, is the right time.
Oh no. A really sad moment. My condolences are with him. RIP.
And you can't find typical business rules on Stack Overflow.
Heh. Thanks for raising. I am very well aware of it.
Getting this right is much harder than it sounds.
Let's call a duck a duck. Unless, you tell me you are designing guidance system for NASA, I'd be happy to leave this pedantic discussion aside.
Most code should be implementing business rules in the simplest and most maintainable way possible. I don't need developers "innovating" on my codebase.
Fair dinkum. That's you. You may be biased towards it due to past experiences and I understand it. However, with that mentality where there are no "innovation"(s) involved, you'll only get donkeys that live within the echo chamber. And, may be that's what you want.
My thoughts are with you Woz. I hope you recover soon buddy!
But because they, especially QA & ops, tend to be viewed as lower on the hierarchy they often have lesser talent filling the ranks.
Geez ever wondered why? It is partly due to the "monkey" work that's required. I feel the "ops" world needs a heavy reset (may sound like broken record again: eliminate toil, eliminate side-effects, chicken/egg problems, test? what test? etc..). Geez and I wonder why positions at "FANG" like places require software engineers to fill in the ops work - the engineers, the thinkers and the leaders at these companies understood pretty early on the importance of "engineering" applied to these "ops" and "qa" disciplines.
overburden developers
Given by today's standard, _most_ if not all the code I review out in the wild are these: - Search your question on $search_engine - Land to stackoverflow - Copy - Paste - Write some crappy unit test (important but still crappy IMHO) - CI - Boom land on production
Where is this special fairy of "overburden"'ed devs you speak of?
Very few code today are _true_ innovations. It's a pile of abstractions over abstraction shite.
That is true. It is every one's responsibility to inform mgmt of this and keep open channel.
And vice-versa (should of said).
overburden developers
Please. Doing a perfunctory role does not equate to "overburden". I'll get grads from a third-world who will _happily_ take the burden off these developers if you so insist.
I do think management often has no idea how many different specialties and expertise there are within engineering.
That is true. It is every one's responsibility to inform mgmt of this and keep open channel.