ismarc

CyberArk (Conjur team) | Mid-Snr Infrastructure Engineer | US REMOTE OR NEWTON, MASSACHUSETTS | FULL-TIME The Conjur infrastructure team provides support and internal tooling to the product engineers working on Conjur and Conjur Enterprise as well as a suite of associated products and integrations. Our job is to make sure engineering has the tools and facilities available to do their jobs with minimal infra-related effort on their part. We’re hiring our fourth engineer to help with that effort. ABOUT US

We work on a wide variety of projects with a heavy emphasis on automation, and are striving to increase engineer self-service capabilities. Experience with any specific items in our stack are not required, we expect only that you're a generalist enthusiastic about learning (with our full support of course). There is no on-call aspect to this position, and we have a strong emphasis on sustainable working hours (9-5, five days a week, with meeting-free Focus Friday to work on pet projects).

A quick list of some of our stack: Containers, Ansible, Jenkins, Cloud IaaS (AWS, GCP, Azure etc), Slack, Node.js, github.com, Bash

TO APPLY

Attempt to solve our engineering puzzle (we promise it's fun, submissions go directly to engineering, and it's how all three of us came to work here) at https://www.conjur.org/careers/puzzle/.

A list of the keywords that an automated scanner would search your resume for: https://www.conjur.org/job-openings/infrastructure-engineer/

----

LEARN MORE

- https://conjur.org (our secret service, LGPLv3)

- https://www.conjur.org/careers/ (about our team, open positions)

- https://www.conjur.org/blog/ (our blog, which talks more about who we are and what we do)

CyberArk (Conjur team) | Mid-Snr Infrastructure Engineer | US REMOTE OR NEWTON, MASSACHUSETTS | FULL-TIME The Conjur infrastructure team provides support and internal tooling to the product engineers working on Conjur and Conjur Enterprise as well as a suite of associated products and integrations. Our job is to make sure engineering has the tools and facilities available to do their jobs with minimal infra-related effort on their part. We’re hiring our fourth engineer to help with that effort.

ABOUT US

We work on a wide variety of projects with a heavy emphasis on automation, and are striving to increase engineer self-service capabilities. Experience with any specific items in our stack are not required, we expect only that you're a generalist enthusiastic about learning (with our full support of course). There is no on-call aspect to this position, and we have a strong emphasis on sustainable working hours (9-5, five days a week, with meeting-free Focus Friday to work on pet projects).

A quick list of some of our stack: Containers, Ansible, Jenkins, Cloud IaaS (AWS, GCP, Azure etc), Slack, Node.js, github.com, Bash

TO APPLY

Attempt to solve our engineering puzzle (we promise it's fun, submissions go directly to engineering, and it's how all three of us came to work here) at https://www.conjur.org/careers/puzzle/.

A list of the keywords that an automated scanner would search your resume for: https://www.conjur.org/job-openings/infrastructure-engineer/

----

LEARN MORE

- https://conjur.org (our secret service, LGPLv3)

- https://www.conjur.org/careers/ (about our team, open positions)

- https://www.conjur.org/blog/ (our blog, which talks more about who we are and what we do)

CyberArk (Conjur team) | Front End / Backend / DevOps / Security | REMOTE (OR ONSITE NEWTON, MA) | FULL-TIME The CyberArk Conjur team helps people write super reliable software that's hard to hack. We're building tools that make the best security practices convenient for developers, ops, and security teams. We're hiring engineering managers, product owners, and of course, engineers.

ABOUT US

We're a busy team, thanks to the increasing success of our product: the Conjur appliance secures the entire software development and deployment lifecycle for companies who want to ship features as fast as possible without increasing their risk of security breaches.

We are looking for experienced software engineers to join our team. Conjur engineers work on a wide variety of projects, from integrations with some of today's most popular DevOps tools to moonshot projects that seek to revolutionize the way engineering teams factor in security when deploying applications.

We know that if you're a professional engineer, experience with specific tools or languages can usually be picked up quickly. That being said, Conjur engineers are using the following tools on a more-or-less daily basis:

* Ruby, Rails, Golang, Postgres, and JS

* Docker, Git, and Jenkins

* Kubernetes, OpenShift, Cloud Foundry

* Puppet, Chef, Ansible

FOR MORE INFORMATION

https://conjur.org (our secret service, AGPLv3) https://www.conjur.org/careers/engineering.html (about our team, and our DevOps puzzle!) https://conjur.org/blog (our blog, which talks more about who we are and what we do)

16 year old me had no clue, no help from parents or other adults and teachers that disallowed all calculators that weren't the required ones. I learned about they books of tables from an old man who helped me withmy homework I was doing at the public library, it's likely the only way he knew how. Not to mention, my main source of food during this time was the free school lunches and I was working 3rd shift to help pay rent and utilities, $5 was a lot of money (to us at least, this would have been mid 90s).

I was in the required but too poor group. I had to borrow others or do the work by hand. I eventually was able to get gifted one from one of those "help families in poverty with school supplies" donation drives. I had those books with tables of logarithms and one other one constantly checked out from the public library just so I could do my homework.

I can confirm it's drilled into Army soldiers as well, so I'd bet on the air force and navy being the same way.

I sometimes lose words. Like chair disappears from my mind, I can describe one, I know what one is, but the label for it is gone and even if you say it I may or may not recognize it. I don't have dyslexia, but a mental health issue that causes it. The funny part is names do the same thing, they're labels for specific people.

You are grossly misrepresenting the situation and what your own link says. If wages + tips don't equal the normal minimum wage of $7.25, the employer is required to make up the difference.

They get, at worst, normal minimum wage.

My 2011 only has the gas gauge, without any gallon markers on it and numerous 2016/2017 cars I've been test driving haven't had it. It's certain classes of cars that have had it for quite a while, nowhere close to all.

Invodo | Test Automation Engineer | Austin, Tx | Onsite full-time, Remote for the right person.

Not going to post the whole job description here, it's available at http://www.invodo.com/careers/test-automation-engineer/. We're looking for a developer with a strong testing/QA background or a QA engineer with strong development background. If you have questions, or are interested but don't think you meet all the requirements, drop me a line as well.

Reachable at mbrace@invodo.com

You're showing your ignorance of what it's like to be poor. It takes time and money to get to those locations, two things the poor don't have. The bus trip, or train, or gas in a car that's used has to cost less than what the app would gain them and that money/time needs to not be slotted for anything else (such as making it to and from jobs until payday).

Someone elsewhere in the thread said that the poor aren't good with managing money. From my experience, it's the opposite. Imagine you're behind on every bill, with less money coming in than it costs to have electricity, get to and from work, eat and pay rent. You literally rotate which bills get paid based on what will be shut off next. If someone gives you $100, you could pay more of the bills, or put it in savings, or spend it on entertainment/something fun. In 3 months, no matter what happens, you'll be back in the same state you are now. Spending it on entertainment to feel like a person isn't a bad decision at that point. It's just not one that those who live privileged lives would make

Our use-case is different (not cassandra or db hosted on ephemeral drives), but what we've found using AWS for about 2 years now is that when an availability zone goes out, it's either linked to or affects EBS. Our setup now is to have base-load data and PG WAL files stored/written to S3, all servers use ephemeral drives, difference in data is loaded at machine creation time, AMI that servers are loaded from is recreated every night. We always deploy to 3 AZs (2 if that's all a region has) with Route 53 latency based DNS lookups that points to an ELB that sits in front of our servers for the region (previously had 1 ELB per AZ as they used DNS lookups to determine where to route someone amongst AZs and some of our sites are the origin for a CDN, so it didn't balance appropriately...this has since been changed) that is in the public+private section of a VPC with all the rest of our infrastructure in the private section of a VPC (VPC across all 3 AZs). We use ELBs internal to the AZ for services that communicate with each other. The entire system is designed to where you can shoot a single server, a single AZ or a single region in the face and the worst you have is degraded performance (say, going to the west coast from the east coast, etc.).

Using this type of setup, we had 100% availability for our customers over a period of 2 years (up until a couple of weeks ago where the flash 12 upgrade caused a small amount of our customers to be impacted). This includes the large outage in US East 1 from the electrical storm, as well as several other EBS related outages. Overall costs are cheaper than setting up our own geo-diverse set of datacenters (or racks in datacenters) thanks to heavy use of reserved instances. We keep looking at the costs and as soon as it makes sense, we'll switch over, but will still use several of the features of AWS (peak load growth, RDS, Route 53).

The short answer is to design your entire system so that any component can randomly be shot in the face, from a single server to the eastern seaboard falling into the ocean to the United States immediately going the way of Mad Max. Design failure into the system and you get to sleep at night a lot more.

You've obviously never had any real interaction with someone in the grip of a mental health emergency. She was put on suicide watch and evaluation, not because it's just fun. She cut the shit out of her leg, to where it bleed through, had repeated, documented thoughts of suicide and then tried to just pretend everything was OK. The first night was emergency care, i.e., make sure she didn't die. The next days were mental health evaluation while making sure she didn't die. You cannot be forcibly admitted in the U.S. she admitted herself. She did not have to stay after the first night, but they will make you think you do because they want you alive and to help you get better. It's not some giant conspiracy to do harm to people.

Does mental health services suck pretty much everywhere? Yes. But nothing she went through was inhumane (I've been through similar scenarios in less pleasant medical facilities) and all of it is geared to try and help.

I was on a medication that did something similar (I believe it may have been depakote or gabapentin). Thing is, I have absurdly good relative pitch, and combined with an 'internalized' sound of 60Hz (I've worked around a large number of generators and high voltage equipment over the years), I have the same net effect as perfect pitch (60Hz is roughly a quarter step above B-flat, a quarter step below B).

What bugged me was the intervals were off. It's hard to describe, but, for those not familiar with how the notes are laid out, 60Hz is quarter step below B, 120 is quarter step below B, 240 is quarter step below B, and so on. However, as you get higher, the frequency difference gets larger (B is actually 61.75ish Hz and B flat is 58.25ish Hz, next higher is 123.5ish Hz and 116.5ish Hz, and so on). Things were translated ~1/4 octave higher, which completely threw everything off because the 60Hz sound no longer fell evenly between two notes or even directly on a note, it was an 1/8th step away. This meant that as the notes got further away from 60Hz (higher or lower), the distance to the note got larger. So while everything was still evenly in tune, my guidepost began to really suck.

Long story short: I have no idea why it did what it did, but it was freaky. However, it was probably the most amenable side-effect I had from the medication.

When I first used oop, or any object orientation, it was in the early days of the public internet. There wasn't nearly the resources available now, especially for a hobbyist. So when I learned the syntax (I believe it was early c++), I had nothing else to go on. I naturally leapt to using objects to describe and build new data types. It made me think about what data I needed, then how the data needed to be operated on. It wasn't until I started taking courses that I heard the noun approach... And it just seems completely backwards. It isn't about modeling your data, it's about the conceptual items you're working on. I still think oop is a good approach if you ignore all of the 'best practices' and instead use it to build custom data types that simplify your algorithms. It's part of what I really like about Erlang records (even though they're a bit annoying to use) and Scala in general. You can build custom data types without having to just compose lists and maps but you get a lot of the benefits from functional programming.

I really don't understand why so much of the programming classes, tutorials, guides and common wisdom aren't 'data first' style design.

Peppers are particularly difficult to cook with. Their oils are what is spicy, so you get variations based on growing conditions as well as how you prepare it. To reduce spiciness, remove all seeds, rinse with cold water and put it in a cold salt water bath for a couple of hours. Not enough to change the flavor, but just until you start to see the oils collect on the surface. This only works with raw peppers. If you then lightly sear the outside, you can get more of the flavor without the spiciness getting into the rest of the food as much. With the right sized pieces, you can then pull out the spicy chunks and still have the nice flavor.

You should have a look to see how much memory the connection tracking table is actually taking up. IPTables stores a lot of its information in kernel space, but modifications are copied to user space, updated, then written back. As an example, for large project X with >100,000 users connecting through a linux-based gateway device, using a single firewall rule to allow access for each device grew larger than RAM available to the kernel. You can also tune the size of the connection tracking table (and pretty much everything else related), but 64k sessions was never a breaking point for us.

There may still be. The first two I opened were closed pointing to docs on how to set the writing stuff. The reproduction is pretty easy, if a shard tries to write its results to a shard that is write locked, none of that shard's map reduced data after that point is written to any shard. The more evenly distributed your data, and the more shards you have, the more likely you'll hit the condition. Combined with the fact that all unsharded collections always go to the same shard, the whole system becomes useless unless you can fit your entire dataset in all collections in ram on a single box.

Any particular advice on how to not lose data when map-reducing from a sharded collection into another sharded collection? Because we had to migrate away from mongodb in a hurry when we had ~20-40% of our data just not get written (basically 1-2 shards worth) from that scenario. And by in a hurry, I mean we spent a significant amount of time debugging, troubleshooting and tracking down what was causing the issue (we were on 2.2 at the time, not sure if it's been fixed since...) and realized there was no way to fix the bug unless we were willing to delve into how mongo did the writes from map-reduces. So once we found the underlying issue, we quickly migrated away.

The number of conditions where it will silently lose data and you have no control over the write consistency is absurd. However, every time it's brought up, people shout it down because they assume you're talking about the known (32-bit version and dataset size/ram size, not setting it to confirm the write, etc) write issues, and not completely different ones that aren't resolvable.

HUDs use light focused at infinity so the point of focus for your eyes doesn't change when looking at the display (it "hovers" mid-air). Holographic sites, HUDs, Google Glass all use the same principle, with varying ways of getting the light onto your eye (curved mirror that changes the focal point of the light properly that reflects on a piece of glass, a piece of glass curved to focus the light properly when it's projected on it and a lens on the projector to focus the light properly are the 3 primary approaches).

I recently got back into regularly riding (I now regularly commute to/from work on my motorcycle) and I completely agree. However, I absolutely would love to have a HUD, but not anything people keep thinking you need a HUD for. A decent GPS unit + bluetooth or smartphone + bluetooth is good enough for those "I got lost, now need to get home" rides. I don't want any sort of communication provided on it. I want a real HUD, giving me real time, easily interpreted information about what's going on around me.

I envision something closer to aircraft/fighter aircraft HUDs:

  * Roll indicator
  * "target indicator" (in this case, any non-stationary object).  Can be as simple as a diamond shape near the center of the detected target
  * Visual indicator of direction/speed of the target (something like a line from the diamond as a 3d projection for where the diamond will be in 4 seconds based on current speed/direction)
  * Similar direction/speed indicator for you

All of the HUDs I see coming out (Google glass included) seem geared towards providing you information to distract you from what you're doing, not enhance it, which is the opposite of what I want.

The source that the quote is pulled from (Schiebinger, Londa (2001). Has Feminism Changed Science?. United States of America: Harvard University Press. ISBN 0674005449) includes (in the very next paragraph):

"In 1996 salaries for women in professional fields increased to 85–95 percent of men with similar jobs. Younger women in the United States (childless women between the ages of 27 and 33) earned nearly the same (98 percent) as men in their age group."

The quote from the National Science Foundation in the book is unsourced, however, the only related information from the National Science foundation I could find was http://www.nsf.gov/statistics/issuebrf/sib99352.htm which is not necessarily contradictor, but paints an entirely different picture.

While I disagree with who you are responding to, there has been a massive improvement in 1 1/2 generations and it removes a significant amount of credibility to present information in a way to try and say that widespread systemic discrimination still occurs in areas where it does not.

It goes both ways. I wrote a chunk of code for reactos years ago that got pulled into wine, had some fixes done by other folks in wine and then those fixes pushed back to reactos. Both are audacious, with different goals but extremely similar work along both paths.

I was in the military, with a clearance. You describe it reasonably well. A clearance means you can have access, if needed. I am completely against collection of information as they are doing because of time. A warrant gives them access to data from all time. This is a departure from current warrants that allow them to collect and examine data starting now (or as far back as it was stored by external parties). It's the difference between getting a warrant to wiretap a phone and getting a warrant to listen to every phone call ever made with a phone. In my mind, a warrant says we have have reasonable suspicion to collect more information as it stands right now, not reasonable suspicion to examine past behavior. Then again, I believe that the U.S.'s definition of rights are great and should be extended to all humans by the U.S., not just citizens or those on U.S. soil.

I've been working with websockets on AWS for some data intensive bi-directional communication and haven't had any issues with it...However, I don't have it set up as an HTTP listener, I have it set to TCP 80 -> TCP <mylocalport>. The server architecture doesn't matter if a user drifts backend hosts if their connection drops and reestablishes (no stickiness needed). I haven't tried it under the HTTPS setting for SSL connections yet, but if there's flakiness, I know I can just terminate SSL on the ec2 instances instead of the ELB.

For a helicopter, you need a hangar, a pilot, regular maintenance, insurance, fuel/oil as well as membership/pad fees if you actually want to fly anywhere besides airports. You could do a small helicopter for $200,000-$400,000 and then about $30,000-$40,000 a year in recurring costs before pilot, fuel and oil. You can expect $300-$400 per hour of flight time. If the 10 million is invested and has a return of 4% annually, the helicopter will cost 10% of the max you can pull out without depleting principle. That also doesn't include loan payments if you didn't buy the helicopter outright.

So, helicopter money is a lot higher than it looks.

For the 'Like who?', I'm too lazy to check which companies are our customers that have a "can be used to endorse our service" clause, the categories off the top of my head are: major telecom providers, major PC sales companies, office furniture sales companies, major clothing companies, major beauty product companies. Note that this doesn't cover new companies or technology focused ones, there's a particular demographic that they are selling to that at a minimum browse their sites while at work. And after rereading everything, I may have been a bit ambiguous, so I'll clarify. People, while they are at work, use browser A because they work for shitty company X. While at work, they browse, add to cart and buy from an unrelated company. And for whatever reason, people buying from the unrelated company are disproportionately doing so while at work and working for a company with outdated browsers.

For the degradation, I especially don't mean a lazy approach. In fact, having good degradation is typically harder for newer developers (or requires them to check in more browsers). The core way to do it is to develop for what's common across browsers (what's handled the same way), then for ambiguities in the spec (does the border count as part of the width of a div or not?). Once that's done, you then add the extra. The idea is, if browser A supports, say, easily defined gradients on a button, but browser B doesn't, should we have a special case for browser B to load an image to give the identical gradient, or should we let it be a flat colored button? Or let's say a browser has some extensions that make client-side form validation easy and simple. Using that functionality for that browser makes sense, but is the development effort to do the validation on all browsers worth it when server-side validation will happen also? The functionality is the same, the experiences are both good, but the experiences are not identical.

You're missing an important part of this. There's a large number of companies whose web capabilities need to support people who use their website while working at the companies that have older versions of IE. The company I'm with has embedded video players on a large number of web retailer's pages (we're hiring a javascript+flash developer in Austin, TX right now, particularly around video players. If you're interested, drop me a line) and a significant portion of them have requirements to support IE6 or IE7 with analytics that back up the need based on percentage of their traffic and conversions from those users.

However, I (not speaking for the company, just me personally) strongly disagree with the focus on "identical experience" amongst browsers. Instead, I prefer the route of graceful degradation where not all features may be available for all browsers, but it's fully functional and aesthetically pleasing (not necessarily identical) in all browsers.

That being said, not all companies have the same browser support requirements...it's entirely based around what the site's individual traffic and conversion rates are.

It's actually more complex than that. You can use val and def in the same places. The difference is when it is evaluated. val has the right hand side evaluated immediately (such as, if it's a class member, it will be evaluated when the class is constructed). def has the right hand side evaluated every time it is referenced. So, val x = 5+5 would evaluate 5+5 and assign to x. def x = 5+5 would set x to a function that takes no parameters and returns an int, but if you had, say x + x, that function would be called twice, resulting in a value of 20.

This difference is stark when you look at what it's doing, but allows for some interesting uses when combined with lazy vals. We use it pretty extensively in our configuration loader (using twitter-eval) that allows us to do per-value overrides of configuration files by using lazy vals assigned to defs and then using the defs in the application (of all the performance bottlenecks we have, the possibly optimized out function call generated for the defs is negligible). The end result is that you can derive values from configuration settings prior to the configuration finishing being loaded. This means we don't have to care what order the configuration files are loaded in (they're separated by what they're configuring, with many shared between applications).

I have a tattoo on each of my forearms, one says "love life" and the other says "embrace death". I got them while I was in the military, but independent of being in the military. I had a friend (unrelated brother would be another term) who was shot and killed by his father in law. He knew it was coming, he may have been able to avoid dying himself, but didn't. I had spoken to him about life and death multiple times, and he always lived such that if he were to die that moment, he wouldn't have any regrets, but he clung to and enjoyed life. I'm not going to go into the full story of the details surrounding his death (I am willing to over email if anyone's really wants to know), but I got the tattoos shortly afterwards as a constant reminder. It's about being the person you want to be, doing the right thing even if it isn't the easy thing, living life so that if you died right now you could be proud of how you lived your life.

I have met very few people who live their lives the same way (many claim to, or even do when it's the easy path, but stray when it's not) and there are many people who have similar experiences but go on to just live in fear, or eventually put it to the back of their minds. Everyone, death is inevitable (even if we somehow achieve immortality, there's the heat death of the universe). No matter how long or short your life is, you decide where it goes and you are the judge of the quality of how you lived that life.