Also, if you have a slightly older workstation, your tab on which teams run will definitely crash. Mostly.
436 karma · joined January 14, 2018
Also, if you have a slightly older workstation, your tab on which teams run will definitely crash. Mostly.
1: https://www.mozilla.org/en-US/firefox/96.0/releasenotes 2: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Rel...
In my cynical view, When you think about engineers as people who want to stay up to date with 'latest and greatest' so that they are not left behind in the market, the use of their frameworks makes sense. Also, the frameworks do solve very key problems in their own ways (and also avoid re-inventing the wheel).
So the truth lies somewhere between the 2 sentences there. There's nothing which we can not achieve without frameworks however managing that solution is a pain. More so if one is working on a bigger team.
But then, I learned of how to give credits and all, but once you are "marked" there's very little chance that you may get monetized (at least used to be that way, haven't checked now). Also, by default, your videos would be marked as "Has copyrighted contents" which might not always be true.
The biggest pain point comes when you have to argue with the system / support. There were 2 videos where I did not use copyrighted material and credited royalty free track as per the requirement but there's no winning over them(even with facts).
For an organization as big as the Big G, this automated system and lack of actual checks until someone with big following tweets at them is sad to see even in 2021.
Now it is just what it is called, "Related videos" (which you are most likely to see)
and since they asked all about my experiences and what was written, I was able to articulate more than I would in usual tech rounds.
Although we couldn't agree on location for personal reasons, that is an org which I would recommend specially as they really wanted to know the candidate's behavior and not whether he could remember some implementations which they're mostly never going to use.
wouldn't it be easier to select an item with ID than select one with a class name and then iterate over to find which one you want. I am talking about items which exist only once. I am still not clear on why not to use IDs in a page in your opinion.
wait a minute, does everyone NOT use IDs for unique elements on page (not each element)? I mean I am genuinely interested in knowing why not to use IDs. There are unique elements which need to be selected on a page like #logout or something.
Safe to say you have a verified way of backup and restore (with worst case data loss of an 1 hour).
I am not exactly an expert on what stage does Transaction ID Wraparound comes in but still know that as one of the key criticisms of PostgreSQL so wanted to check.
Also, 7 days backup with versioning switched is a smart tactic! Thanks once again for this.
Did you have any instance where you needed to restore the DB / Have you done restoration tests to ensure this is a feasible solution? Also, since you are using local postgres DB, do you not run into issues like transaction id wraparound ?
Also, how many days of backup you keep on S3? Considering you create 24 backups a day.
I read such messages (and also agree to it mostly) and then I encounter my peers wanting active-active clusters with K8s on top or something and I feel I like a dinosaur.
Refreshing to see KISS still being used. Also gitea. What an awesome piece of open source software.
This feels true more and more.
So, not sure if this fits the question - spent a lot of time learning new tech, focusing on non-tech for a short period of time. I feel that I have been overlooking that side of skill-set.
Oh my god this is so true for me too. I had really strong opinions on so many things that if I put aside my ignorant opinions about them, I / my life / career would have been better. Strong opinions I had included I don't need to use OOP in PHP (had to until too late), Bitcoin is worthless who would ever invest in it (had to until too late / costly), NoSQL is just useless, what's so wrong with PostgreSQL (had to swallow my words until I used Redis), so many more. The current opinion I am holding is "who needs Kubernetes" when individual VMs do the trick and slowly but steadily I feel these words will be regretted too.
Interesting. Read about this elsewhere too (but that was subject to a negotiation) but yeah, I think it might help in not getting hung up on a single rejection / company so to speak.
Does that not impact the performance / coding stages?