You're preaching to the choir with Jira alternatives. For devs, Jira more often gets in the way than helps. We're ok with a minimal set of features. In order to really get traction, you need to sell PM's and leadership types.
The RTO push for 3, 4, or 5 days a week for devs is simply unreasonable. The company I work for encourages (but doesn't mandate) 1 day per week, which works great for us. You can then spend more time helping junior coworkers, having in person discussions, and happy hours for that day. It's a good minimum to feel connected. Obviously, it all depends on what type of role you have.
WhatsApp had a blip of popularity in the US back in 2013, but people moved over to iMessage, Facebook Messenger, and Snapchat in the years since. I mostly blame the design, since WhatsApp was quite hard to look at for years. I get the feeling that people in the US view WhatsApp as old technology. I still use WhatsApp occasionally to talk to friends from European countries, and especially if I'm on vacation somewhere in Europe. But then again, the same goes with WeChat and China. The feature set in all the messaging apps are comparable. You have to remember how large the market penetration is for iPhones in the US, so the default is iMessage (which falls back to SMS).
This is the framework used for Gravity Circuit, the Mega Man X inspired game that came out last month. It’s one of the best games of the year, by the way. I’ve been interested in exploring this framework. Glad to see it’s gotten attention on HN
RTO after 3.5 years isn't a return from temporary working habits. Many big companies have structured their teams around not needing to be co-located. RTO is like transitioning from the cloud back to on-prem. It is a complete realignment of the way your company works.
What made AOL truly great was instant messaging and chat rooms and focus on "connecting people". They had the vision totally correct, but the implementation details wrong. They should have transitioned from an ISP to a social media site.
We are excited to introduce the AWS Elastic Icon Identifier, a service designed to simplify your AWS Management Console navigation by quickly identifying AWS service icons. This service offers Icon Recognition, enabling you to instantly identify an uploaded AWS icon; an Icon Library with a continuously updated collection of AWS service icons; and API Integration, allowing you to programmatically identify AWS icons in your applications. Additionally, it ensures High Availability with extra redundancy layers and built-in Fault Tolerance to handle unforeseen issues without service impact. This not only accelerates the learning curve for new users but also helps experienced users efficiently identify unfamiliar icons or refresh their memory on lesser-used services.
The pricing is designed to be cost-effective for all users, with a Free Tier of 100 icon identifications per month, a Pay-as-you-go plan at $0.01 per icon after the first 100, and a Premium Plan at $10/month for 1000 identifications, with extra identifications at $0.008 per icon. All plans include unlimited access to the Icon Library and API Integration, as well as High Availability and Fault Tolerance features at no additional cost. For more details, visit our Pricing page on the AWS website.
Start simplifying your AWS experience with the Elastic Icon Identifier today!
Back in 2010, most devs were using Java or C++. As any C++ dev will tell you, setting up 3rd party dependencies takes forever especially on Windows. In comes Python with its simple yet powerful core language features, batteries included philosophy, and tons of easy to install packages. That attracted a lot of attention from C++ and Java devs looking to get things done easier. It also attracted attention from systems developers looking for a saner alternative to writing Bash scripts. Not only that, but because of the simplicity of development, it became a core teaching language for learning programming. And because of all of that, it became even more popular when more math-oriented people needed a language to use for AI/ML.
Ruby fits a lot of the same niches. I also remember experimenting with Ruby at the same time I was experimenting with Python. There's nothing necessarily wrong with Ruby.
But it's an either/or situation, like HD-DVD and Blu-Ray. Ruby fell into obscurity almost because of the rise of Python. Because we now have a solid ultra-high level language with batteries included, there's less of a need to also focus on Ruby.
The categorization of developers into just 'front-end' and 'back-end' is an oversimplification that doesn't capture the full spectrum of roles in software development. There are many other specializations such as full-stack developers, who touch several different layers including the UI, as well as DevOps engineers, who focus on the deployment, monitoring, and maintenance of applications. Moreover, a large percentage of roles are more specialized like data engineers, security engineers, mobile app developers, and more.
The goal of modern CAPTCHAs is to determine if the user is "acting like a human". Deciphering warbled, blurry text worked in the days when OCR was difficult. As we can see, that rule no longer applies. Now, it should be about making sure behavior is typical or atypical. Is this a human browsing the web, or is this a script using AI to pass captchas?
We came in with big expectations, but it’s too bare bones to be useful yet. Main problem is lack of searchability (is us-east-1 down? How’s the Uber waits at the stadium? What was that loud sound just now?).
It was a reaction against Elon Musk, and the desire to find a Twitter-like social network that's more human focused with less news, etc. But it's very bare bones right now. You can't do a lot of the common things that made Twitter so good, such as searching to see if AWS us-east-1 is down by people posting tweets.
If we want to be pedantic, C++ is a high level programming language. Newer languages like Python just provide a higher degree of abstraction, so you could call them "higher-level programming languages".
After the disaster with 3rd party apps, Reddit needs to make some big changes to keep its userbase. Elon already saw how vulnerable Twitter was when Threads attracted 100 million users in 1 week.
The startup boom was taking advantage of vulnerable companies that had simple operations, but were severely lacking behind in technology. For example, Uber when taxis were still largely cash only and had no apps. Construction is highly technical, complex work.
I really love this concept. While I do get better results from GPT-4 for AWS questions right now, AI as the "interpreter" for documentation works really well.
It's a bit different, since we're early adopters. The average person hasn't spent dozens of hours with GPT-4 yet, and doesn't realize how useful it is to everyday life.
I wouldn't mind Edge if it were a Microsoft branded version of Chromium. It started out that way, and it was nice. But it's attracted every team at Microsoft and a total explosion of semi-useful features until it became totally bloated.
I really enjoy not having to get out of the car to pump gas in New Jersey, and it's nice not taking the chance of getting my hands all smelling like gasoline. It doesn't usually take much longer than pumping it yourself, unless you're at a very busy gas station with only one worker.
Remember the days people thought they could build everything in UML diagrams, and have the code essentially be generated or trivially written from there? Fast forward to 2023 and we're generating UML diagrams from C++ code because it's easier. I love this.
What would be really powerful is an API compatible alternative to Reddit. There's a ton of already developed apps just itching for a new platform to use them with.
The bitcoin craze was just about making money. Buy low, sell high. The different with AI is it's immediately useful for people to do their jobs more effectively, just just a vague "in the future" kind of thing.
Typically Discord, but Discord has its own issues. When the Digg meltdown happened, Reddit was already a Digg clone at the time (this was the days before subreddits).