danny_taco

I'm the lead developer in an org where due to the nature of servicing multiple stakeholders that have a lot of say on what we build - we're building these these types of monstrosities where everything is configurable so it takes dozens of clicks to go anywhere and the end user is not a priority.

Yesterday I almost cried. I've started dusting off the old resume, catching up on my craft and I plan to go back as a senior software engineer in a consumer facing project at a remote first organization, wish me luck.

To me it does the opposite. It shows that Apple communicates and cares about security for their users. I don't see how them addressing and responding to Google's claims makes them appear in a worse light. To each his own I guess.

I often leave early or come late to work and my employer doesn't care as long as I get the work done. As long as I'm there for meetings where I have to be there, everything is good. Perhaps you should talk with your employer about their expectations from you so you don't feel like you have to be there for 8 hours from M-F.

This is fascinating. Can I ask your reasoning behind this behavior?

It is native on iOS but not for desktop.

It's quite clever actually, why spend resources to try and infiltrate them - which is not a guarantee, when you can pay a fraction of the cost for their capabilities so you can focus your efforts on other nation states or your own citizens.

I stopped putting my telephone number on my resume years ago. I realized I would start getting spam calls more often (and this was years ago) whenever I started passing my resume around to recruiters or applying directly to companies.

If they want to reach me, they can do so my email, and it has worked fine so far.

This is par for the course for Accenture. I joined Accenture to work on a very interesting development project for a fortune 10 a few years ago. A project that could have been done in 6-8 months by a competent team in a reasonable budget. But being Accenture, it turned into a mess of epic proportions with the client threatening to sue.

In the end we ended up delivering this piece of software that I wouldn't touch again with a 10-foot pole, which didn't even satisfy most of the original business requirements. The exec from the client that hired us changed the narrative to his stakeholders to make this appear as a big success, and the project even got a lot of coverage on the internal newsletter when in reality it was just a smash and grab of a dozen or so million dollars from a client that got swindled so bad that they wouldn't even admit it.

I ended up being mostly on the bench for the rest of my stay at Accenture while watching every single one of the individuals that worked on that project leave for better pastures. A year in after the project started no one that worked on it was in Accenture anymore, except me. I was conflicted if I wanted to leave because I would hit the gym for two hours every day at around 2-3pm, then go home. My mornings were full of reading blogs, working on personal projects and just gossiping by the water cooler. In the end I decided to leave since I missed doing real work and working with a competent team. That year was one hell of a ride for me.

I love this analogy

The reason Slack is buying HipChat if you were to ask me, is to take over the on-prem market for chat apps - given that they're loosing money by not going after this market. When looked at it from that perspective, the purchase makes perfect sense.

As for Microsoft Teams, they don't have to be on premise since all the big corporations that use on-premise only have for the most part adopted Microsoft 360.

I was going to click it then realized you need to pay $1. Interesting experiment nonetheless.

This is exactly why we moved out of Firebase once it got acquired by google. We knew support would become nonexistent and we would also run the risk of Google shutting down the service for no good reason.

I think you are confusing right to work with at will employment.

As someone that was made to sign a confidentiality agreement under duress and unfair pressure months after joining the company, with stipulations that basically say ANY work I do, regardless of industry or during the weekend, belong to the company. Even after I no longer work there up to one year, and ONLY if I bother to sign the attached clause that says I no longer work there.

I'm so glad that tomorrow I'll be handing in my two weeks notice especially at a critical time for the company. I'm also the most senior developer that everyone else comes to with questions regarding how the system works and how it can be improved. The original developers left for similar reasons.

What I'm trying to say is, if you think, as a business owner or employer that you can act against the best interests of your employees then you'll end up paying dearly for it one way or another.

I'm surprised the police followed through with the information from the victim. I went through the same after being burglarized and I couldn't do anything because the detectives didn't care and/or were unreachable. This was in Houston though.

For a brief time I worked on a DARPA program to develop platforms for the DoD to plan to conduct and assess cyber warfare in a manner similar to kinetic warfare. It was a really interesting project with very difficult problems to solve.

This is a perfect example on how not to handle professional conflict. I would point out all the mistakes you've made and that is just from your point of view as described in the article but everyone else here have pointed those out.

For your own sake I suggest you take this down, otherwise you may find it difficult to find work later on. If you are ever in a similar position like this again you need to learn to not take things personal and walk away while you still have some dignity.

I would consider that salary as extra income for multiple earners in a household (You wouldn't be able to rent any decent place with that amount per day). Although the cost of living in Juarez is way way below than most places in the US, the cost of utilities in Juarez is unreasonably high. I couldn't find a lot of online resources to support this though. https://goo.gl/beC6LK

I grew up in Juarez and despite my parents making at least ten times that amount between the two of them, I would say we were only considered middle lower class for a household of four people.

The city has grown over the past 30 years considerably due to the manufacturing industry. https://en.wikipedia.org/wiki/Maquiladora

Most of the jobs provided by the maquiladora industry are low wage jobs such as this one that attract a lot of struggling families or individuals from other Mexican states. Some of my old friends still live in Juarez given that they work as industrial engineers and their salary ranges between $30,000 - $40,000 USD. Just enough to buy a 2-3 bedroom home in a decent area of town. This is a comparatively high salary for the region as well.

While I agree that having you jump through these hoops is really time consuming and annoying, for most if not all companies it's a necessary evil in order to identify potential employees. How else do you assess a potential employee? It's gonna be either through whiteboarding/live coding with the interviewer(s) or through you portfolio, which your github repos and contributions serve as a good example.

Having said that, some companies take it to the extreme, and honestly they sound like a more traditional office type of environment where I doubt you want to work at from what I can infer from your comments.

I also do not agree with the assumption that only the privileged have time to contribute to open source (aka free projects). You either do it because a) you love it, or b) because you need to beef up your portfolio and you are motivated enough to do so. I'm considered a minority in the tech industry as well, yet I got into it many years ago by working on pro bono projects after going home every day from my telemarketing job at 2.am.

Either in technology or in any industry, you'll get your foot on the door and you will advance faster if you enjoy what you do. This is easily recognized by potential employers when they see you participate in hackathons and that you contribute to OSS.

Sure, I began doing free projects to get into the industry, but I keep doing it today because I love it and that's what makes it so easy for me to find employment as a software developer. In fact I get contacted by recruiters at least twice a week on linkedin and it's somewhat annoying. I hope Anna learns enough at her job to the point where she'll be able to easily find a job and be able to recognize toxic environments that make you jump through excessive hoops.

Just my 2 cents.

That is certainly good news. Keep up the good work!

The problem we found with using AppGyver is that you depend on them for your builds. Once you finish making your app, you deploy to AppGyver then go to their website and click a button to build a compiled application. Also, keep in mind that is not uncommon to wait up to 10-15 minutes for a build. When you are on the clock, this add up.

Like others have mentioned, it's a framework on top of a framework on top of a framework. You will find breaking points and get frustrated. Are you trying to use custom Cordova plugins? Well, the build failed. Here's an error report of what went wrong. Go make the changes necessary and build again while waiting for another 10-15 minutes.

So, you built an Angular application on top of AppGyver with the native navigation. Actually, you built many little applications where each one works in one of the native views. If you are trying to port this into a web app you are SOL.

These are my thoughts on AppGyver, from a developer that used their stack for a few clients. These days I'll either go RubyMotion or Emberjs/Cordova.