Bad guys from batman

Good Cop, Free Donut

2009.11.06 05:08 SaveOurSouls Good Cop, Free Donut

All cops are not bad. This page is for the good guys. Why should the bad guys get all the attention? Trolling and anti-cop sentiment are discouraged here. Troll posts and anti-cop content can be removed per moderator's discretion. Violators will be banned.

2011.07.03 08:16 Amazon Mechanical Turk Reddit homepage


2022.06.08 07:12 AlternativeAd3842 [email protected]@]] 2022 Full Movie Streams in HD for FREE

[email protected]@]] Fantastic Beasts: The Secrets of Dumbledore Full Movie,The Lost City Streams,Morbius Online,Sonic the Hedgehog 2 Free,Memory Full Movie,The Northman Movie,Watch Jurassic World Dominion Movie,Uncharted 2022 Movie,Doctor Strange in the Multiverse of Madness Movie,Spider-Man: No Way Home Movie,The Batman Movie,Turning Red Movie,A Day to Die Movie,The Contractor Movie,The Exorcism of God Movie,The Bad Guys Movie,Gasoline Alley Movie,Chip 'n Dale: Rescue Rangers Movie,Moonfall Movie.

2023.03.21 10:55 EmployerDifferent482 [Profile Review] Asian 32M, GPA 3.8, ex-consulting, LBGT, GMAT N/A

Hey guys,

I'm very new to this place and hoping to get a sense of my odds. Targets are Stanford, Wharton, Booth, Sloan, Haas, Yale, Tuck and Fuqua

- UG in mech engineering 3.77/4, from a public state univ with US News overall ranking ~50 and engineering ranking 8~10
- Master in management 3.79/4, from an elite private univ with US News overall ranking 8~10
- GMAT N/A, targeting at least 730

[Work] (all are in China)
- 1 year at a US BB bank (while not IBD apparently), trainee program at the commercial banking
- 3 years at McKinsey but not typical consultant. I started as a research role and turned into expert consulting track with more client facing. Focus on FIG sector. Had fully staffed on maybe ~5 projects doing basically the same work as a BA/Asso does. Another ~5 projects as a expert role mainly participated during the early stage and important client meetings. Other times (with great life balance) mainly worked on research support, internal knowledge solutions and also worked with partners on many biddings...
- 2 years at a corp strategy team (but actually more like an internal research institute) in a Chinese big name in TMT/Entertainment. Mainly working on industry/sectocompetitor study for management reference. I'm not a manager role but have been leading project teams of ~3 so kind of playing EM role (definitely not the same extenstiveness)

- Already 32 years old though only 6 years of work experience (how does this affect my odds?)
- Asian, male, LGBT, first generation (I don't really like these tags but anyway)

[Career Goal]
- Post MBA I plan to work in the US problly starting with consulting again and settle down at a corp role in the end/ or find some interesting start-up to work for. Also open to investment field because my focus at McKinsey was around asset management and had served a few top US banks and funds.
submitted by EmployerDifferent482 to u/EmployerDifferent482 [link] [comments]

2023.03.21 10:55 CheckOutTheseAbs At what point do you feel comfortable exercising your right to self defense?

So, you're out shopping and you see a man with a rifle slung over his shoulder. You have a pistol and by the grace of the unproven holiness the next shot you fire will be a 100% accurate kill shot (the guy has a real bad diet, even shooting him in the foot would kill him even without space magic).
View Poll
submitted by CheckOutTheseAbs to VaushV [link] [comments]

2023.03.21 10:55 Optimal_Following_44 Attract A Girl By Black Magic / Vashikaran Baba Ji, +91-7300250825 >>>

Attract A Girl By Black Magic / Vashikaran Baba Ji, +91-7300250825 >>> Black Magic Specialist Baba Ji Do you believe in black magic? Some people do, and they believe that there are people who can use this dark power to help or harm others. Baba Ji is one of these black magic specialists, and he claims to be able to help people with their problems. Are you curious about what he can do? Read on to find out more.
Do you believe in black magic? Many people around the world do, and they often turn to specialist practitioners like Baba Ji to help them with their problems. Baba Ji is a well-known black magic specialist in India, and he has helped many people with his powers.
Whether you believe in black magic or not, there is no denying that Baba Ji is a very powerful man. If you are facing any problems in your life, it may be worth giving him a try.

Black Magic Specialist Baba Ji

Do you believe in black magic? Some people do, and they claim that there are specialists who can help you with this dark power. Baba Ji is one of these specialists, and he claims to have helped many people with his black magic skills.
Whether you believe in black magic or not, Baba Ji’s story is an interesting one. He grew up in a small village in India, and he says that he always had a gift for helping people. When he was a young man, he began to learn the ways of black magic from a local guru.
Since then, Baba Ji has been helping people with his black magic skills. He says that he can help with problems like love, money, and health. If you’re curious about black magic, then Baba Ji’s story is definitely worth reading.

Black Magic Specialist Baba Ji

Are you looking for a Black Magic Sexpert Baba Ji?
If you are looking for a Black Magic Specialist Baba Ji, then you have come to the right place. In this article, we will provide you with all the information you need about Black Magic expertBaba Ji.
Table of Contents:
  1. Introduction
  2. What is Black Magic expert Baba Ji?
  3. The Benefits of Black Magic expert Baba Ji
  4. How to Find the Right Black Magic expert Baba Ji
  5. Conclusion

What is Black Magic Specialist Baba Ji?

Black Magic expert Baba Ji is a term used to describe a person who is an expert in the field of black magic. Black magic is a type of magic that is used to harm or kill people. It is also known as the dark arts.
The Benefits of Black Magic expert Baba Ji
There are many benefits of black magic. Some of the benefits are:
  1. It can help you get rid of your enemies.
  2. It can help you get rid of your problems.
  3. It can help you get what you want.
  4. It can help you get rid of your bad luck.
  5. It can help you get rid of your financial problems.

How to Find the Right Black Magic Specialist Baba Ji

When you are looking for a Black Magic Specialist Baba Ji, you need to make sure that you find the right one. There are many things that you need to consider when you are looking for a Black Magic Sexpert Baba Ji. Some of the things that you need to consider are:
  1. The experience of the Black Magic expert Baba Ji
  2. The success rate of the Black Magicexpert Baba Ji
  3. The reviews of the Black Magic expert Baba Ji
  4. The price of the Black Magic expert Baba Ji
  5. The guarantee of the Black Magic expert Baba Ji
When you are looking for a Black Magic Sexpert Baba Ji, you need to make sure that you find the right one. There are many things that you need to consider when you are looking for a Black Magic Specialist Baba Ji. Some of the things that you need to consider are:
  1. The experience of the Black Magic expert Baba Ji
  2. The success rate of the Black Magic expert Baba Ji
  3. The reviews of the Black Magic expert Baba Ji
  4. The price of the Black Magic expert Baba Ji
  5. The guarantee of the Black Magic expert Baba Ji
Are you looking for a Black Magic Specialist Baba Ji? If so, then you have come to the right place. I am one of the most experienced and successful black magic specialists in the world, and I can help you get the results you desire.
Black magic is a very powerful tool that can be used for good or evil purposes. If you know how to use it correctly, you can achieve amazing results. However, if you misuse it, you can cause great harm to yourself and others.
I have been helping people with black magic for many years, and I have a very good success rate. I am confident that I can help you get the results you desire.
If you are interested in learning more about black magic, or if you need help with a black magic spell, please contact me. I will be happy to help you achieve your goals.
Are you facing problems in your life that you can’t seem to overcome? Do you feel like you’ve tried everything but nothing is working? If you’re feeling lost and helpless, there is still hope. A black magic specialist baba ji can help you turn your life around and get rid of all the negativity that’s been holding you back.
submitted by Optimal_Following_44 to u/Optimal_Following_44 [link] [comments]

2023.03.21 10:54 Mgiwar no matter how bad people try to kill us. no matter how bad people try to prevent us from getting out of the concentration camp. I will try to get out of the concentration camp of the corrupt fascist Pushilin. The shelling continues.

no matter how bad people try to kill us. no matter how bad people try to prevent us from getting out of the concentration camp. I will try to get out of the concentration camp of the corrupt fascist Pushilin. The shelling continues. submitted by Mgiwar to u/Mgiwar [link] [comments]

2023.03.21 10:53 CryptographerLast155 AITA for kissing my wife and telling her I love her?

I, (m29) and my wife (f29) have been married for about two years, she is absolutely the love of my life and I am so beyond lucky to have married her. We were friends for a while before we began dating so I knew her family pretty well before we began dating.
My wife has three sisters, two younger and one older, and to put it bluntly her older sister does not care for me at all, she’s made it clear she doesn’t believe that I am good enough for my wife and she could do better. She has been married the last decade, she got pregnant at 18 so they believed they needed to get married to appease his family.
About a month ago she came over to my wife and I’s home sobbing saying that her husband had left her for another woman? leaving her with their four kids. Although we don’t have the greatest relationship she is still family so I felt really bad for her, so for the last month and I my wife and I have basically spent all of our free time with my sister-in-law and our nieces and nephews, I even helped her haul boxes of her ex-husbands stuff out of their house one a very cold and rainy day, which also happened to be my one day off that week. We have also been helping out financially by helping with rent, bills and groceries.
Yesterday morning my wife was taking my sister-in-law out for a girls day, when I dropped my wife off at her sisters place I kissed her and told her that I loved her. Her sister watched all of this, I could tell her mood dropped when she saw us. After I left, I got a call maybe 20 minutes later from my wife asking me to pick her up.
I did and my wife was pissed, she told me sister-in-law had blown up at her, calling us insensitive to her situation and horrible people for not putting a stop to the PDA while she was around. My wife and I are not super into PDA but we always kiss whenever we say goodbye so I didn’t realise it was a big deal, my wife told me my sister-in-law has been making it a huge deal and calling up other family members to try and get them on her side. My wife is pissed and I can’t help but feel like it’s all my fault. So AITA?
submitted by CryptographerLast155 to AmItheAsshole [link] [comments]

2023.03.21 10:53 No-Psychology1751 Dormando’s Ops Mantra


The Technical Element

Design for change

- The old google mantra is right. Design for change. Change is having to deploy new software, upgrade existing software, scaling, equipment breaking, and people shifting around. - Everything in this mantra is about finding balance. You might think it's a good idea to tightly marry your system to a particular OS or Linux distro. It's just as bad of an idea to separately them entirely. Use layers and a _little_ indirection if you must. - This does not mean complete and total platform agnostics. It's about making one system two, two systems twenty. Dealing if a sysadmin gets hit by a bus, if that dangling harddrive dies, if someone runs rm -rf /. It's for the incremental changes. Security updates, pushing new corporate content.

Use automatic, repeatable builds

- Don't build anything by hand. If you do, do it twice, and grab every single command the second time around. - I cannot stress how important this is. It should take no more than 15 minutes from bare metal to production for new hardware. There does not need to be a human element to screw it up, or get punished when a server goes down and no one knows how to replace it. - This is true for anything. There is _no_ such thing as a "one off" server build. If you've built it once, and it only needs to exist once, it will exist twice. The second time around is when it breaks, or if you need to do a major upgrade or consolidation two years down the road and have no frickin' clue how it was put together. - Test, vet new builds. This should be easy because your builds are all automatic, correct? - Scripted builds means that upgrade from Linux Distro Version 3 to Version 4 is absolutely clear cut. Install Version 4 and test the scripts. Read documentation and fix until it works again. This should be a week's worth of work at most, not a yearlong project. (to finish just in time for Version 5 to come out!).

Use redundancy

- Just beacuse something might be easy to rebuild, doesn't mean you can ignore redundancy. Jump boxes, mail servers, billing gateways, whatever. Wouldn't it be a hell of a lot easier if you could swap out one half of the equation without causing downtime for your customers? - ... and along those lines, you get to "deal with it later!" when a box goes down at 3am, and the redundant machine kicks in. - Even if it's not ideal, go for it anyway. Rsync'ing configs to a second box is a step above nothing. DRBD might not be perfect but it can provide an amazing service.

Use backups

- We shouldn't even joke about this. Use harddrives, burn the tapes. Compress them, move them, run them in parallel. Backup EVERYTHING! - If your builds are automatic, the entire process can be backed up. If you're following along past this point a *real* Disaster Recovery plan might not seem so far fetched.

Keep monitoring specific

- Monitor every damn thing you can, but do it right. Don't get a thousand alerts if your NFS server craps its pants. Don't alert on timeouts if it doesn't make sense for your system. Test for success at the most specific level; sure the service might allow a new TCP connection, and it might even say hello, but does it remember how to do its job? - If you have 500 webservers, you probably don't need to know immediately if one goes down. You _should_ know if the load balancer decided to not take it out of rotation and real human people are seeing its uglyriffic error messages.

Graph data, keep exact historical data

- Graphs are for visualizing trends. Historical data is for crunching numbers. Don't mix the two! It's too easy to get wrong numbers from eyeballing graphs. Many sites use rrd's or other aggregating data systems which will average and smooth out data over time to save on storage space. This means it's not only hard to read, it's wrong. - Don't get trapped having to skim through hundreds of graphs just to pinpoint an issue. If you're trying to find outliers in the graphs, you can pull those out via scripts as well. - If you must use graphs for troubleshooting, try to aggregate high level concepts into a single page, which link into drill-down pages from there. If you can see a spike in the database load, you'll know to click to the page overviewing the databases, then you'd see the one or two iffy machines in question. The idea is to narrow something down fast. Remove as much guesswork as possible.

Log useful information, use multiple streams of data

- Work on your own, and with development, to log as much useful information as you can. Doesn't matter if you live analyze it and store the data somewhere, or lump it into a database and run reports. Information is useful. - Useful examples: Page rendering time (what page, what box, etc), user-facing errors, database and internal service errors, bandwidth usage, etc. - Establish graphs, reports, and do historical comparisons from generalized data. - Reports are really important. Get digested data week-to-week or day-to-day about changes in your infrastructure.

Understand your data storage, databases

- There's an entirely separate set of undrestanding about operating databases, but sometimes you can't leave all of this up to your DBA. - Having multiple, redundant databases affords you many luxuries. Operations that were once many hours of downtime can be done "online" without shelling out for a huge Oracle instance. MySQL and replication is a fantastic thing. - Work with the DBAs to get the best possible hardware for the database in question. RAID10, gobs of RAM, many fast spindles, and potentially RAM disks and SSD's. Ops has access to the vendors, DBA's can beat the pants off the hardware. Find out what works best and save tons of cash in the long run. - Database configurations are changing. Software like HiveDB, MySQL Proxy, DPM exist now. We're absolutely doing partitioned data for huge datasets. We're also thinking outside of the box with software like starling and Gearman. Learn what these are, and understand that not everything will be in a database. - Get a good grip on your filers! If the data's important, back it up! Snapshots on monolithic NFS servers are fantastic, wonderful, and NOT a backup! - Consider alternatives. MogileFS gets better year after year. There're likely other projects for freely and cheaply maintaining massive stores of files. Similar systems were developed for,, etc. We're finally free of expensive NFS filers being the standard!

Scale out a lot, up a little

- You've seen all of the papers. Scale out is really the way to go. Get commodity (read: available, affordable, standard, NOT super cheap) hardware and work with everyone to ensure all aspects possible can scale out. - Scaling out starts at two, work from there. This also happens to encompass redundancy. - Scale out as far as you can without being idiotic about it. The example of MySQL replication with single master, many slaves, is a fantastic example of one form of scale-out sucking. All slaves must do all writes, so as the number of writes scale up with the reads (if they do for your app, which I bet they certainly do), you get less capacity per slave you add. - Keep alternatives in mind. User or range partitioning onto many databases, avoiding production slaves where possible, etc. Good ideas, many ways of implement. - Everything can scale if you give it a chance! Routers, switches, load balancers, webservers, databases. - Remember scale up? Big evil machines with many slow cores, lots of IO boards, and very expensive storage equipment? They're coming back. Well, the CPU part is. - RAM is cheap. - Combine the two, and you just may end up combining services again. A load balancer here, a webserver there... If an application can use many CPUs (apache) this is perfect. If it can't (memcached doesn't get much benefit from it, usually) you can end up wasting tons of available resources by segregating services too much. - Job systems could potentially fill in gaps here. Where there're extra cores, slap up more workers.


- Caching is good. Developers, sysops, etc. Get on this! Yes, it's weird. It's different. Sometimes you may even need to, gasp, make a tradeoff for it. Effective use of caching can have as much as a ten times increase in overall system performance. That's a giant magnifying glass over the systems you have already and a fraction of the overall cost. - Memcached. Service cache, denormalize DB structures (where it makes performance sense!), squid cache, or even make better usage of OS caches. - Test it, toy with it, and break it. There will be new and different problems with caching. Be prepared for it.

Asyncronous jobs

- Starling, Gearman, The Schwartz, whatever. Job systems allow much more application flexibility. Workers can be spawned one-off, be persistent (load cached data, prepare data, etc), be on different hardware, different locations, and be syncronous or asyncronous. - Maintaining these things is an ops issue. Using them is both a developer and an ops issue. - User clicks "send all my friends an e-mail". Schedule a job, immediately say "okay done! Your friends will receive your spam shortly!" - let the job service multiplex and deal with the issue. - Job systems are great places to bridge services. Blog post -> IM notification, billing cron -> billing services, authentication gateways, etc. - Easy to scale. There will be choke points for where requests come in, and all the workers need to do is pull. This is in contrast with the largely push/pull state of HTTP.

Security and patrols

- Install security updates! Seriously! There's a whole crazy network of people who are dedicated to giving these to you in the shortest period of time possible. Don't let them sit for _years_ because you're afraid of change. - Security is in layers. Accept what you can and cannot secure. Just because mysql has password access doesn't mean it gets to be directly accessable by the internet. - Disable passwords over ssh. Use passphrase encrypted key auth. Remote users _cannot_ guess your private key. They _have_ to get it from you. Keep it safe, and there's no point in firewalling off your ssh port. - Understand how the application works, exactly what it needs to do, and work that to your advantage. If the only part of your application which needs outbound internet access _at all_ are the billing pages and some twitter-posting service, those can easily become job workers. Put the job workers on specific boxes and allow those access to specific hosts. Keep the rest of your network in the dark. - The above is especially important for php sites, but probably works great elsewhere. If someone breaks in, it's most likely going to be through your application. When someone gets in through the front gate, they'll need to haul in their toolbox to get into the safe. Don't let them pull in data and get what they need, or upload the contents of your database somewhere! - These specific suggestions aside, read a lot. Use your best judgement, and test. If you have no understanding of how a security model works, that might not immediately make it worthless, but you certainly don't know where its limits are or even if it works. - Secure based on testing, theory, attack trees, don't stab in the dark. I love it when people dream up obscure security models and ordinary folks like me can smush it to crumbles. - Patrol what you can! Audit logins, logouts, commands used. All accesses to external facing services, including all arguments given in the request. Find outliers, outright ban input outside of the scope of your application, and do what you can actively and have the data to work retroactively. - If you suspect something's been cracked, *take proper precaution* and understand a little computer forensics (or get a company that does). Respond by removing network access, checking the system through serial console or direct terminal, and avoiding using any service, config file, or data on the compromised machine. Too many people "clean up a trojan' and never understand how it got there, or if they've _actually cleaned it up_. - If you do have a security team, forensics expert, or anyone else onhand, you must touch the machine as little as possible and isolate it. This means not rebooting it to "clear out some funky running processes". They need to be able to get at those. If you need to half ass it, go ahead, but remember to wipe the system completely clean, apply any security updates, and do your best to figure out if they've compromised any important data. Do what you can. - Security is an incredible balancing act. If you do it wrong, developers, users, etc, will revolt and find ways around it. If they _can_ get around it, you're not doing your job right. If they _can't_ get around it, they might just give up and leave. - Keep an iron grip on access control. This means ops must absolutely provide windows for what doors have been locked. Kicking development off of production entirely means they get to stab in the dark on fixing hard problems. Providing logging, debugging tools, etc, without allowing them to directly change the service, will be a win for all aspects of production.

The Human Element

Learn from many sources

- Fill up some RSS feeds, and read at least a few good articles per week. LWN, kerneltrap,, whatever's relevant, or even loosely related, to what you do. - Read blogs from smart people. Sometimes they post interesting topics, and comment streams give us the unique ability to directly converse with the masters. - Read a few blogs from not so smart people. Get a feel for what stumps them, or what they do that doesn't work so well. - Get to know people who can kick your ass, at anything. Stay humble. - Help find your own strengths by taking in from many sources, and gobbling up what envigorates you. - Read up on success and failure stories from other companies. Ring up their CTO's and get them to divulge advise over free lunch.

Try many things

- You'll be amazed at what you can do if you keep trying. Never seen something before? Give it a shot. - Try to not be a dangerous newbie. Play in the sandbox until you're comfortable enough to not burn down the house.

Understand redundancy

- Really understand how redundancy affects things. How it works, how it doesn't work. - Break redundant systems in a test lab, sometimes in production. Learn what you can while you're in control. Unplug the power, yank cards out, kill processes, run the box out of memory, yank a harddrive, yank ethernet. - Test replacing and upgrading systems in a redundant setup. Maybe you can toss in that brand new hal-o-tron 8000 without taking downtime.

Understand scalability

- There're tons of papers on making scalable systems. Even if you can't write one yourself, try to understand the theory. - Learn with virtualization. Set up a few virtual machines and try tossing up applications to multiple machines. Run multiple instances locally on different ports. - It's usually the job of operations to do proper capacity planning. You won't know what to do add unless you truely understand where resources should be added.

Become a troubleshooting superstar

- The moment something breaks the clock is ticking. You must be able to pull out your arsenal and use them effectively. - Practice troubleshooting. Pick a perfectly good, working page, and try to track down how it works. - strace, ltrace, lsof, logs. - Understand that load != load. Look at all available information as to how a host is performing or behaving. - Be very familiar with the tools for your IO system. Often "mysterious" performance problems happen beacuse your RAID or SAN setup isn't happy for some reason. - Leave documentation. Checklists, troubleshooting tips, build tools. - Build more tools. For yourself, for other people, or add features to existing ones.

Work with IT

- Believe it or not, there is overlap. - Ops has to maintain high bandwidth network access for servers. IT has to do the same for people, and is often the bridge ops has *into* the datacenter. It may make sense to work together on this one. - Draw the right line. IT should manage mail, but ops should manage development servers. Don't offload things you don't need to, and offer to do what you do best if necessary. - Don't alienate people. Macs are popular, linux is (slowly) gaining share. Believe it or not, forcing everyone to use microsoft productivity software can bite you. There are plenty of alternatives, try one. Odds are more people in your company are familiar with google apps than they are with outlook. - Don't make it more difficult than you have to do for people to run a unix system natively. Unless your backend is a windows shop, wouldn't you want people to have more familiarity with the OS they're supposed to support?

Work with developers

- You both work on the same product, for the same purpose. Try working together a little more. - Having strategy meetings is not working together. - Development understands the code resources the best, and operations understands the hardware and deployment the best. You can design something more efficient by taking all of this into mind. - Cross training. Disseminating information can show how tools and designs on both sides can be improved to be more manageable and resilient. - Be careful of being too demanding on either side. It's not an Us vs Them. Everyone's human. Everyone should be doing as much as they can for the company, not for themselves. - It's more pleasent to handle crunch times and emergencies when everyone gets along.

Work with ops

- Ops folks have their specialties. Networking, databases, OS. Don't forget to talk to each other! - Getting stuck in a rut is demotivating, boring, and a good way to lose people. Even if your systems ops guy has the ability to look over the shoulder of the network guy, they have the opportunity to learn. - Always give people an opportunity to try, learn, and grow. - Be careful of rewarding your best with too much work. If there're people who can pick up slack, you use them. - Bad eggs. It happens. Be tough enough to deal with them. Most people can be turned around with a little help, but they need to be able to be independent.

The Practice

Fix it now, not later

- If a webserver goes offline, don't care about it. You have ten spare, right? - Pick a day during the week to sweep up broken crap. Replace any broken hardware, ensure everything's 100% before swinging into the weekend. - If small, annoying problems crop up, fix them permanently first thing in the morning. Logs fill up the disk twice last week? Come in fresh the next day, and fix it for good. These stack up, and suck. - If you have automated builds, use this to your advantage to fix what you can right away, or in bulk.

Automate everything

- Humans can't screw up scripted tasks (as easily). - Do it twice. Once by hand if you must, then roll up what you did into a script. - Commented scripts make fantastic documentation. Instead of writing twenty pages detailing how to install something (which is up to interpretation of the reader!), write a script which explains what it does. - Scripts can be rolled up into automated builds. The more often something is done, the closer it should get to becoming a zero time task.

Change what's necessary

- Make small, isolated changes. - If you don't have to change it, leave it. - This also means you must understand _when_ to change. Find what's necessary and upgrade it, switch it out, make it standard.

Design for change

- If you can't do it right immediately, get on the road to it being right. - This means if you don't have time to do something right, get the basics going with a clear migration roadmap to the right thing. While your new mail system might not be the crazy cool redundant bounce-processing spam monster you dream of, installing postfix and setting up two hosts with a clean configuration gets you closer than you might think. - This does have a tendency to leave unfinished projects everywhere, but you were going to do that anyway. :)

Practice updating content, fast

- It's usually the job of operations to push out code. Don't suck at it. Push in parallel, apply rolling restarts, be an efficient machine. - This includes software updates, security patches, and configuration changes. - Use puppet, cfengine, whatever you need to control the configuration. Keep it clean, simple, and easy. - The fewer files one must change to make a necessary adjustment the better. If you're adding one line to 20 files just to push out a new database, you're doing it wrong. Build simple templates, build outward, and don't repeat data which needs to be edited by hand.

Standardize, stick to the standard

- Pick one or two standard OS's, httpd's, databases, package systems. - Stick with them. Adjust and upgrade methods as it makes sense. - Don't stick with that major version forever. Unless your product is going to be feature frozen forever, you'll need to keep the standard rolling forward, and everthing behind it. - The _more_ is standard, the more places your tools will work. The more packages for other parts of the operation will "just work" everywhere else too.

Document well

- Document process - Document product - Categorize into shallow trees. - Don't redundantly document. If a script has a long help, ask the reader to refer to that. The closer the documentation is to the program being discussed, the more likely it is to stay accurate. - Marry documentation into code. perldoc, pydoc, etc. - Out of date documentation is poisonous. Reserve time to keep things up to date. Sit down with new employees and update documentation as they run into problems. - Use ticketing systems, with moderation. Documentation of history is important as well. Forcing people to create detailed process tickets for a DNS is just pissing in other people's cheerios.

Use source control

- Use git, or mercurial. Avoid SVN like the black plague. - Put all of your configurations, scripts hacks, whatever, into source control. - Keep checkouts everywhere... - Keep strict, clean, master checkouts. No one should be able to push changes that aren't comitted, but it should also be easy to test changes (in a VM, directly on a single test machine) without having to wrestle with the source control.

Hire well

- Discern between stubborn and smart - Don't avoid hiring senior. Some people really know their shit. Some _seem_ like they do. Others are "senior" in a particular area and will fall behind as technology changes. While you might want to avoid some, there are definitely rockstars out there. - Don't avoid hiring junior. I know so many people who've started really junior (including myself! I still view myself as junior), who've shot up through the ranks and are now have firm established careers. I'd believe most of us have. Except there are ones who don't learn, don't have the motivation, or are in the wrong field.

Avoid vendor lock in, and keep a good relationship with the vendors you do use

- Buying propreitary hardward has the major downside of potentially locking you into always using it. It might be a particular SAN, NAS, special-case direct attached storage, backup systems, etc. Avoid getting sucked in. If you follow all of the above design advise, one should be able to build test environments on different platforms quickly. You're then able to keep on top of hardware evaluations and keep choices open. - If everything's deep, dark, gnarled, undocumented, and directly dependent on your fancy proprietary load balancer, you'll never wriggle free of it. - Be nice to the vendors you do end up using. If you "push them _hard_ on price!" for every single purchase, expect some shit hardware to show up. - Datacenters these days have a lot of potentially useful resources. Try to throw some free remote hands service into your contract and abusing that to get harddrives replaced, vendor items shipped/RMA'ed, and some basic hardware installs. I've had entire racks of equipment delivered and installed with barely a visit from an employee... and damn, it's nice.

Give Open Source a serious try

- nginx, mongrel, lighttpd, apache, perlbal, mogilefs, memcached, squid, OpenBGPD, PF, IPTables, LVS, MySQL, Postgres, blah, blah, blah. Before you hop back on that trusty, reliable, expensive proprietary setup, give open source a shot. You might find yourself adding plugins, extensions, code fixes or contracting help to bring features you'd never be able to do otherwise. In my own experience OSS is just as reliable, often moreso, than big expensive hardware when put under significant load. - The idea of "you get what you pay for" is a complete lie. If you can't make OSS work for you and need the hand holding, you _can_ still go with a vendor. If you have a smart, motivated team, who really want to learn and understand how their infrastructure runs, you just can't beat some hardy GPL'ed or BSD'ed systems. - MySQL and Postgres are fine. Call them tradeoffs if you will; nothing's going to crawl out of your closet and night and eat your data. Sure, it does happen, but you're much more likely to be screwed over with monolithic oracle instances going offline (it happens!) than you are with a well tested and stable MySQL instance, in a redundant master<->master cluster pair. - I'd say 'cite references' - but go look around. Check out any number of articles on the LAMP stack. Most major dot coms, ISP's, and even corporations now are adopting. Give it a shot. The worst you'll have is some lost time, and another product to scare your vendor into dropping price with.
submitted by No-Psychology1751 to sysadmin [link] [comments]

2023.03.21 10:53 TreeHarald Dynamics ruining the game (story)

I'm playing in the lower leagues of England and have been fighting my way upwards. For those of you who have done that type of save you will know that the finances are always tricky to handle, but I have gotten into a situation where the save is simply ruined for me.
One of my players demanded a new contracted right after the transfer window closed. Thing is, I had no money. The club is in red finances, no wages or transfer budget to use. Cant sell the guy, No loans to cancel or clauses to sell out. I request more money from the board and they deny it.
Now, we are top of the league and doing wonderfully, but I have to tell the player that the club cant afford a new contract (additionally he is demanding 4x what he is on and is a bench warmer). He says he won't accept it and gets furious.
Fast forward a couple of weeks and some failed attempts to reopen talks with his agent, and I have a meeting with the Team leaders. One of the leaders agree but the other two gets furious.
The team leaders then starts spreading shit and the dressing room is now in shambles and we are loosing matches left right and centre. Worst part is, those two team leaders are icons at the club , have a great relationship to me and are my favorite players. I bought them to the club and they've played for me for 5+ years. The betrayal is real.
Im obviously selling him this january, but its just infuriating that 1 little shit can ruin the season. Plus, I probably need to sell those two team leaders cause I am pissed off and petty.
Okey, rage over. Back to fm.
submitted by TreeHarald to footballmanagergames [link] [comments]

2023.03.21 10:53 Least_Diamond1064 List of bugs I have encountered in the game

Literally just a list of all the bugs I've found in Freelancer. Hopefully the devs catch on to these and patch them. They're not fun enough to be features.
  1. Bug where a target NPC spawns far off the map.
  2. Bug where NPC spawns far under the map, but can teleport to the correct location (happened to be an assassin and sent me back to the start.
  3. Bug where NPCs have a brief window of time for spotting you doing an illegal action a half second or so after you do it, usually because I did it crouching and that removes the animation.
  4. Bug where rusty nail/rusty crowbafuse cell can't be picked up in the safehouse.
  5. Bug where you can shoot in the Safehouse (this one I'm okay with)
  6. Bug where NPCs pick up unpoisoned glass/beverage from within the poisoned one, making it impossible to poison them.
  7. Bug where camera doesn't zoom in when looking at crates in Freelancer.
  8. Bug where camera doesn't zoom in when aiming with a gun.
  9. Bug where briefcase gets knocked out of bounds by being behind a door.
  10. Bug where an NPC can shoot you through a wall.
  11. Bug where civilians can notice you committing serious crimes (like dragging a body/hiding a body) through walls.
  12. Bug where you spawn and can move around, but when the game fully loads, jumps back to the starting location, sometimes causing you to fall through the map.
  13. Bug where your suitcase and other items spawn underneath the map.
  14. Bug where items don't load in your inventory immediately like in the main game, and can lag your game or delete items that haven't spawned in yet if you begin playing. This is annoying because I have to wait a few seconds to make sure all of my stuff hasn't been teleported to the nether, but also useful because I can carry two large items into the game and the lag is so bad they won't load in until I'm far enough away from civilians around spawn.
Long story short: Freelancer is filled with bugs, there's no way I can show visually all of the bugs, but if you've experienced them, you know they're an issue.
submitted by Least_Diamond1064 to HiTMAN [link] [comments]

2023.03.21 10:53 w1ntermadness Felt like showing you guys my new custom snare drum from W.odd Custom Drums

Felt like showing you guys my new custom snare drum from W.odd Custom Drums submitted by w1ntermadness to drums [link] [comments]

2023.03.21 10:53 Mgiwar no matter how bad people try to kill us. no matter how bad people try to prevent us from getting out of the concentration camp. I will try to get out of the concentration camp of the corrupt fascist Pushilin. The shelling continues.

no matter how bad people try to kill us. no matter how bad people try to prevent us from getting out of the concentration camp. I will try to get out of the concentration camp of the corrupt fascist Pushilin. The shelling continues. submitted by Mgiwar to u/Mgiwar [link] [comments]

2023.03.21 10:52 GraceOfEscanor Parents

I feel like my parents (Mum) only acknowledges I’m autistic when I’m freaking out having a meltdown, then she can be the ever so supporting mother calming down her crazy son. When I exhibit all my other traits then I’m just me being “hard”, badly behaved or simply over dramatic.
Anyone else deal with this?
Sorry to be mundane just tired of being the ungrateful arsehole every time I shut down from stress.
submitted by GraceOfEscanor to autism [link] [comments]

2023.03.21 10:52 DrakharD BTFP and how the Fed and US Treasury decided to print additional $4.4 trillion (12.03.2023) - implications for crypto

A short note:
My previous post was deleted due to rule 8. - on topic discussion.
Dear mods please consider this "on topic discussion", as implications of their decision will heavily impact crypto.
During the COVID money printing episode ($4.189 trillion), Bitcoin rallied from $3k to $69k. What will it do this time when we can expect and additional $4.4 trillion injected.
Assets like gold, real estate, and (obviously) Bitcoin would be an obvious way to hedge from this.

An excellent article by Arthur Hayes, if you have time check it out, I'll condense it to reddit format.
BTFP (Bank Term Funding Program) is the newest brilliant idea from The Fed and US Treasury that will allow them to print additional $4.4 trillion.
The reason why this is happening is there are hundreds of banks in same position as SVB and they need a bailout.
A quick summary how we got is here:
  1. Banks deposit base ballooned, and they lent money during a time when interest rates were at a 5,000-year low.
  2. As interest rates rose in response to the Fed raising its policy rate, the bond and loan portfolios of these banks nursed large, unrealized losses.
  3. Depositors wanted to get paid more interest than they were getting from their regional banks, so they started leaving to invest in higher-yielding products like money market funds and short-term US Treasury bills. The banks couldn’t stomach these losses because they couldn’t pay the Fed Funds Rate to depositors, since the interest they were earning on their loan and bond portfolio on a blended basis was far less than that rate.
  4. The market always knew this was going to become an issue eventually, but it took the failure of Silvergate and then SVB to fully drive home just how severe it was. And as a result, every single regional bank is now assumed to be on borrowed time.
So the FED and US Treasury put out a plan - BTFP.
Document with details is here.
I'll break it in sections.
  1. You need to be a US bank to partake in the program.
  2. Financial instruments eligible for use as collateral under the program are largely limited to US Treasury debt and Mortgage Backed Securities. With cutoff date FED set to 12.03.2023, the scope of program is $4.4 trillion
  3. There are no size limitations. If your bank holds $100 billion of UST and MBS, you can submit that total amount to be funded using the BTFP.
  4. The Fed’s money is priced at the 1-year interest rate. Given that short term rates are well above long-term rates, this means banks, for the most part, accrue negative interest over the life of the loan. Even though losses are bad, they get to exchange underwater bonds for 100% of their value, rather than recognizing losses and going bankrupt. Everybody keeps their job, except for the poor sods at Silvergate, SVB, and Signature. The first shall be the last …
  5. And maybe most important issue. The program is stated to only last one year …when has a government ever given back the power that the people gave them during a time of crisis? This program will almost certainly be extended preemptively — otherwise, the market will throw a big enough fit to demonstrate it needs its fix of printed money, and the program will be extended regardless.
So what are the implications?
The Fed printed $4.189 trillion in response COVID. Right off the bat, the Fed implicitly printed $4.4 trillion with the implementation of BTFP.
Important to note that program will only accepts collateral on banks balance sheets as of 12 March 2023, and ends one year from now.
But as author alluded, what if government does not end the program. Has government ever given back control or power they grabbed during crisis?
What we have here is infinite money printing machine.
submitted by DrakharD to CryptoCurrency [link] [comments]

2023.03.21 10:52 theblues2022 What do you guys think of my extra landing? Took a couple of go arounds to get it after having fun flying through the Grand Canyon (clip from my stream)

What do you guys think of my extra landing? Took a couple of go arounds to get it after having fun flying through the Grand Canyon (clip from my stream) submitted by theblues2022 to MicrosoftFlightSim [link] [comments]

2023.03.21 10:52 RedSpaceDruid Kami nomi zo Shiru Sekai: Girl's Side

Good day. Sorry for the intrusion, but I was interested in one question and therefore decided to ask the members of the otome-fandom.
Kami nomi zo Shiru Sekai is a manga that started in April 2008 and is popular with the harem and bishōjo fandom. The plot is about a guy named Kauragi Keima - a master of bishōjo games, but at the same time he hates reality with everything (Reality is a lousy game!). However, by chance, he concludes a contract with the demon Elsie, and the essence of the contract is to free the girls from the spirits that have settled in their hearts ... and for this it is necessary that the "3D" girls fall in love with him (fortunately, the memory of what happened disappears after an exorcism).
There is a lot of fanfiction for this work. Unfortunately, despite the fact that the manga explores romance games, there are no otome-themed fanfictions. In those cases when the protagonist's gender is changed .... only the gender is changed. Therefore, there are a number of yuri fanfictions, but the topic of otome is not disclosed. There is a fanfic where there is a female analogue of Keima as a "god conqueror", but again, the specifics of female romantic games are omitted and she exists only because she is a secret fan of the "god conqueror". So the idea is a female protagonist who is a master of otome games but hates 3D guys. And by chance, she must make the guys fall in love with her.
I'm not very good at otome games, although I'm familiar with shoujo manga. The question is what specific differences should be taken into account first of all?
submitted by RedSpaceDruid to shoujo [link] [comments]

2023.03.21 10:52 Mgiwar no matter how bad people try to kill us. no matter how bad people try to prevent us from getting out of the concentration camp. I will try to get out of the concentration camp of the corrupt fascist Pushilin. The shelling continues.

no matter how bad people try to kill us. no matter how bad people try to prevent us from getting out of the concentration camp. I will try to get out of the concentration camp of the corrupt fascist Pushilin. The shelling continues. submitted by Mgiwar to u/Mgiwar [link] [comments]

2023.03.21 10:52 o-Persephone-o Virtual assistants applying for US tourist visa

Hi, guys. I am currently working as a healthcare virtual assistant and I am planning to apply for a US tourist visa soon.
For other context, I used to work in Singapore as an ER nurse but didn’t apply there before because situation is different back then and I never thought of going to US for vacation pa, lol. mas gusto kong umuwi ng Pinas during my annual leave to be with my family. So yung back and forth ko lang before to PH and SG ang travel history ko (if that would count) until I decided to go home kasi gusto ko na lang mag-work from home to be with my family.
Yung family kasi ng boyfriend ko lives in US and they’re encouraging me to apply for one para makasama ako sa pagbisita sa kanila by the end of the year and I thought it’s a great chance for me to have a vacation na din.
Are there other VAs out here who applied for a US tourist visa and actually got approved? May I ask for some tips and advices po? What documents I should prepare?
If you got denied, I’m also all-ears po to hear your experience and your advices too.
Thank you to everyone who will respond and help.
submitted by o-Persephone-o to buhaydigital [link] [comments]

2023.03.21 10:51 herkisstheriot where to find (preferably food grade) diatomaceous earth on oahu?

i think my cat has fleas, going to get flea meds from the vet and want to start treating my house before it gets bad. but nowhere seems to ship here online and i haven’t been able to see it in stock on any local hardware store website. is it banned, shown only in stores, or just really hard to acquire here?
submitted by herkisstheriot to Hawaii [link] [comments]

2023.03.21 10:51 AkselXXVII Need testimonies for EU shop

Hello guys, I recently heard about Weiss Schwarz, learned about it, did some research and decided I wanted to start collecting cards.
But as a person from France I'm struggling to find lgs that sell Weiss stuff since it seems to be pretty niche here.
So I checked the 'About' section and found some online store recommendations such as IanTCG and I was wondering if anyone had ever ordered from this store and how was it? Are the boxes mapped? Does it ship fast? And from experience how are the prices for an EU store?
submitted by AkselXXVII to WeissSchwarz [link] [comments]

2023.03.21 10:51 Ok-Incident4915 Facts are false when Incels say them

Facts are false when Incels say them submitted by Ok-Incident4915 to doomer [link] [comments]

2023.03.21 10:51 Puzzleheaded_Bed7070 When the Dice Gods want your character DEAD!

Alright, so I've spent a lot of time binge watching Crispy's Tavern, Critcrab, DnD Doge, Sir Knox, etc. and figured I'd tell this story here.
Now this isn't exactly a horror story in the traditional sense (such as bad DM, bad player, etc) but more just an absolute gobsmacking by the dice gods.
So during one campaign of a group I played Pathfinder IRL with for many years, we were a good many months or year even into the campaign and I forget what happened to my first/original character. I don't recall them dying, but I think I just was kind of bored playing with them or built them poorly or such and they left the party or something at the end of a session.
Anyway, I rolled up my new character ahead of the next session, a Dhampir but I forget what class (they were using a heavy repeating crossbow as their weapon, though), put a lot of effort into making the character and backstory that would incorporate them into the world (effectively at the time the party was in a town where there was a lot of vampire shenanigans going on so it was a perfect time/way to fit the character in who was going to help the party sneak into the head vampire's mansion via a secret passageway with the goal of taking out their kin.) Anyway, they warned there were traps but that they hadn't traversed the tunnels themselves so didn't know what or where.
As the group entered the tunnels, my character is leading the way as they did have the ability to disable traps... assuming they saw them. However, less than 5 minutes into the session I get a roll for perception, with advantage, to scan for traps... I effectively could barely fail (I think I'd need a like 3 or 4 or less to fail)... 2 and nat 1... so I fail to see the trapdoor trap that activates. The DM gives my character a reflex save to attempt to catch themselves on the side of the pit AND one of the other characters a reflex save to attempt to catch THEM if they fail... nat 1... and nat 1... not wanting to kill my character so quickly... the DM gives one more reflex save to attempt to maneuver body to take as little damage from the spikes at the bottom of the pit... silver spikes... (since there were many vampires the vampire lord of the mansion wanted to make sure enemy vampires would be felled by traps if they found the secret passage)... nat... 1...
To the DM's credit, he did everything he could to not kill the character, and even asked everyone and myself if we wanted to just... not. I said no, it was okay, obviously I wasn't meant to play that character if the dice gods were doing that and if they were allowed to live how bad would rolls going forward be? Felt horribly cursed. So after I ended up rolling up something else, I don't remember what.
And that, folks, is the story of how the RNG Dice Gods killed a character I spent hours creating just 5 minutes into the session I brought them to.
TL;DR Created a new character to bring to a game, basically 5 consecutive nat 1s see the character killed instantly 5 minutes into the session. Thanks, RNG Dice Gods.
submitted by Puzzleheaded_Bed7070 to rpghorrorstories [link] [comments]

2023.03.21 10:51 0xSAA Got set 1. Easy AF. Why are you guys saying it went bad?

submitted by 0xSAA to CBSE [link] [comments]

2023.03.21 10:51 FiveLiamFrenzy 39 [M4F] Aussie guy looking to chat with women from all over the world! 😌

submitted by FiveLiamFrenzy to snapchat [link] [comments]