Script author here :-) This was due to two different GitHub Action workflows:
(Workflow 1): Remove the need-triage label under certain conditions.
(Workflow 2): If anyone outside a project maintainer removes a label, re-add it with a friendly message explaining why.
Submitted those at like 10 or 11 pm and went to sleep. Woke up to all issues that got changed overnight with dozens, hundreds, or thousands of these messages.
Cause: Workflow 2 should have checked for project maintainers but also other bots and automation that might also be clearing labels. It got fixed immediately once we realized the issue.
We are working to resolve this. It's still in preview but expect to see healthy Gemini 2.5 Pro allocations for subscription customers in the near future.
Motorola Solutions is growing in Salt Lake City and Seattle and we are looking for DevOps and Platform engineers, as well as a Software Engineering Manager to join our team. The Cloud Infrastructure team is responsible for the development and operations of critical cloud infrastructure and platform services, in support of Motorola Solutions' public and hybrid cloud-based Software as a Service (SaaS) solutions for public safety customers. This team is part of Motorola Solutions’ Software Enterprise division, which offers secure, reliable and efficient team communications, workflow and operational intelligence solutions for mission critical public safety and enterprise markets throughout the world. Our services leverage Cloud Computing infrastructure on AWS to build at scale.
We offer great benefits and the ability to work with cutting-edge technologies, all while delivering mission-critical solutions that literally do change the world.
The Cloud Infrastructure team is responsible for:
* Design and implementation of a continuous integration/continuous delivery (CI/CD) pipeline into multiple public cloud regions
* Development and operation of common platform services that can be leveraged by our SaaS solutions moving forward
* Overall reliability and security of these services and the environments they are run in
* Monitoring and support for these platform and infrastructure services, as well as metrics collection and reporting related to them
Email me at [email protected] if you're interested or please pass on to someone you think might be.
We're now hiring for the following positions in Seattle and Salt Lake City (Engineering in both, Manager just in SLC).
Motorola Solutions | Cloud Infrastructure Engineering Team | Full time | Seattle or Salt Lake City
On any given day, every moment matters to someone, somewhere. And every moment, Motorola Solutions’ (https://www.motorolasolutions.com/en_us/products/smart-publi...) innovations, products and services play essential roles in people’s lives. We help firefighters see around buildings and police officers see around street corners. We keep utility workers connected and visible to each other with real-time voice and data communication across the smart grid. And we provide the situational awareness first responders need when a moment brings catastrophe. We help people be their best in their moments that matter.
Looking for experienced engineers capable of implementing and operating platform infrastructure services, CI/CD pipeline, and data/analytics services on AWS. Ideal candidate has 3+ years experience, writes code (GoLang, Python, Node.js, and Java primarily), and has experience building and supporting SLA-backed production services. Automation fanatics will jump to the front of the queue. Any specific knowledge or experience in the areas of security, CI/CD pipelines, performance/scalability engineering, capacity planning, or AWS serverless computing would be awesome.
Contact me at bryan dot morgan at motorolasolutions dot com
Sorry - I don't think a good job of phrasing my question, although the replies are welcoming for addressing the question of where should we best be advertising.
My actual question was in terms of running ads on our site - I'm trying to determine if all the ad networks are created equal (in terms of payout/CPM) and really what the expected CPM should be for us.
.....although the fact that you say you've looked at it and have no clue what it's about may be my first indication that we still have some work to do :-)
It's a new online community for NFL and college football fans. We have a team of writers producing original content daily, as well as integration with 1000+ RSS and Twitter feeds from the football world. Members can follow any topics they wish - to be added to their own personal "stream" of information - and they can also set their interest level in each topic. Essentially, we're trying to build a true Web 2.0 football site that goes beyond 90's era message boards. The home page, in particular, has been tough for us because we want to highlight our original content but also make members aware of the various streams/communities on the site for each team, player, etc.
Speaking from experience of years as a software architect and now a development manager at a very large technology company, unless you've got a HIGHLY impressive track record of experience, no job worth a crap is going to hire you to work remotely. If you're dead set on it, then as others have pointed out, the freelancing approach (Elance, Guru, oDesk, etc.) does work, to a point. On those sites, you'll always be competing against some insanely low-cost (and low-quality) offshore workers but that's not as big an issue. Again, even on those sites, the issue will be a demonstrated track record of excellence. So, best advice would be to take 3-5 projects on those sites of any size doing anything you feel comfortable doing and don't worry about the $$. Hit home runs on those projects and two things will happen:
(1) There's a very good chance those who hire you will hire you again or extend the projects out
(2) You now have ammo to get other better/more lucrative online freelance projects.
Do the online freelance thing for maybe two years and have tons of good real-world experience under your belt and then you have a shot at landing a full-time remote work position.
A semi-related question to this that we're struggling is: how much should we bother incentivizing those who invite the most with cash, an iPad, or even a contribution to their favorite charity? At the end of the day, this sign-up isn't really directly for people who are going to purchase our service in the future. It's really just a way for people to say "hey, I'm curious - let me know more". We're struggling to determine how much that is really worth.
My guess would be to start by offering a free trial to all visitors. Next on my list would be to identify the top 50 sites that you think most directly reach your target audience and work out some sort of arrangement whereby they offer their members/visitors some sort of discount or deal for using your service.
At first glance, I agree with most others that "the idea itself is worth 0%". Having said that, we all know that's not always true...there's a looooong list of ideas that were so brilliant at the time of their inception that - combined with good fortune and perfect timing - the initial crappy implementation had no real negative impact (hello, Windows 3.0, hello Facemash, etc.).
So your idea may be brilliant...probably not, but maybe so :-) If you have already prototyped it out, have a basic wireframe built, have a good business plan in place, and have some funding lined up (either your own or from some external source) I would say that a technical co-founder would be at most worth 20-25%. From the gist of your question, though, it sounds like you have an idea in your head and that's about it. If that's the case, you gotta find your co-founder and immediately agree to a 50/50 split...maybe give them a 6-8 week 'trial phase' just to make sure they aren't a total fruitcake and are going to bail out on you, then lock it all down legally and move forward from there.
What people are trying to tell you in the other posts is that HARD skills >> SOFT skills when it comes to launching a tech company in the very early stages. Look at your descriptions:
* "business-minded" - hard to quantify
* "action-oriented" - every great developer on earth is this as well
* "team-building" - if you were great at this, your first stop wouldn't be at Hacker News for advice on how to build a team
* "selling" - I agree that this is actually a HARD skill - either you got it or you don't. If you have demonstrated track record in this area, this is your trump card.
* "partnerships" - soft skill...mostly manipulating paperwork with lawyers at the end of the day
* "strategy" - you will easily be splitting this one 50/50 with your technical co-founder
Meanwhile, a good tech co-founder is going to bring:
* Specific dev experience - hard skill
* Knowledge of architecture and scalability - hard skill
* Knowledge of SEO and online technical marketing - hard skill
* Ability to augment his/her skill with other good tech people out there, selecting from their own personal experience or interviewing based on their own skills - hard skill (i.e. business guy has no hope of locating and finding these people, IMHO)
Sorry for the long explanation. Bottom line: you gotta go 50/50. If your guy is not worth 50% in your mind, you have the wrong person.
Thanks for the feedback! It's interesting that #3 seems to running away with it by people who are just providing feedback (none of us who've been working on the site for months would have chosen that one, I think).
We have been experimenting with LaunchRock and will launch our beta invite site in about two weeks using LaunchRock. Actually, we're trying to get some feedback on the background image so I'll submit a separate post asking for feedback on that from the HN audience :-)
(Workflow 1): Remove the need-triage label under certain conditions.
(Workflow 2): If anyone outside a project maintainer removes a label, re-add it with a friendly message explaining why.
Submitted those at like 10 or 11 pm and went to sleep. Woke up to all issues that got changed overnight with dozens, hundreds, or thousands of these messages.
Cause: Workflow 2 should have checked for project maintainers but also other bots and automation that might also be clearing labels. It got fixed immediately once we realized the issue.