I am a DevOps advocate, and as I know, many developers are interested in becoming the DevOps engineers and continue their work in that field. DevOps has become an integral part of the software development field these days. The buzz is around and if you are really interested and want to make some big bucks, start learning and portraying yourself as a DevOps guy. DevOps peeps are now the highest paid people when it comes to the software development world.
Ha Ha, this is funny. It looks like Travis CI is confused now on what to do next. CI is becoming a saturated market. Brand association with students? This looks too childish. Travis CI didn't see this coming though. And the truth is CI tools are being consolidated into DevOps platform or being removed from the market.
The website is straight forward and no gimmicks. You need to do small budget ads around your area just to see how people react to this. You will get some feedback and you can tweak and change the things accordingly. I don't which mode of channel the people of Malawi are mostly on, like Instagram, Facebook or Pinterest, you need to figure it out.
Create stories around your product, just like how you posted in here because people believe stories and they hate direct selling. Don't ever talk about direct selling but always create content around it.
I just did a small analysis, looks like Malawi people mostly like Facebook and Pinterest (http://gs.statcounter.com/social-media-stats/all/malawi) and I suggest you to be on Pinterest too, I believe that visual content can do good for your website.
I also suggest you go to small marketplaces and ask people their suggestions about your product.
This product is for general public so go out there on the ground and get feedbacks. Also, take videos of people who give you good reviews, you might post them on your channel or website.
Isn't this obvious? Do you see those college names, Harvard, Stanford, etc.? Did it ring the bell?
The brand names make a lot of difference when it comes to colleges I believe. For example, take my own case, my friend studied from IIM (one of the premier institutes in India) and I graduated from some other college with much better grades than him, we applied for the same job and the same company, since we are close friends, we did disclose our salaries to each other. What did I find out? His salary is much more than mine; we used to do the same kind of job (I am talking about my first company). So yes, the college names matter.
In some cases, it is pure hustle, they opt for such a category such as AI, Blockchain, ML, DevOps, etc which is unique and niche category with fewer experts and grow in those categories.
Wow, this logo generator is so amazing. Lol, hope logo designers don't get out of the job. But seriously speaking, for small businesses, this is a great tool. I have seen people charging hundreds of dollars just for a logo these days, so this tool is an easy growth hack for startups. Added this to my list of growth hacking tools for startups https://docs.google.com/spreadsheets/d/11JtTcBeZ0U3arpYthIrv...
Yes, I agree. Most of the people/startup guys out there don't want to use the word growth hacking, as they think it seems to have a negative impact on their startup, so the shift is happening from growth hacking to growth marketing. I am from India and I work as a growth hacker, and I am surprised to see how many people actually want to shift their careers from marketing to growth hacking.
Just go to Google trends and see the trend for the word 'Growth Marketing', it is going up.
Not many social media platforms are safe these days. It all started with Facebook's user privacy drama that happened recently. But on a contradict to what I say, the big thing that motivates people to join different social media platforms is whether or not their friends or the 'cool' kids are using it. People are generally motivated largely by crows and if they see their friends or coworkers using these platforms, they will probably join them too to fit in.
We call it 'FOMO', the 'Fear Of Missing Out'.
Basically, your everyday Joe joins because that's where everyone else is. Businesses join because that's where their potential customers are. Websites are there so we can be FOUND, social media is there essentially so we can be KNOWN. But those lines are now blurring.
People are slowly realizing that social media is no fun anymore. So I am liking micro-blogging and interest-specific social platforms like Pinterest and WONDR(https://mywondr.co/).
First of all, SEO is more of common sense.
- It should start with creating a persona for your potential buyer/customer
- You need to know your potential keywords
- Analyse what your potential customers might search for
- You need to understand the intent of the search because there are different types of keywords, all keywords are not created equal. You need to hit those pure buying intent keywords but in a subtle way
- You need to do proper keyword research. I have created a keyword research template to help you all https://docs.google.com/spreadsheets/d/168CBn10UK31sMw-fnP8k...
Yes, in the end, content is the king. Give them what they want, they will come back again.
With your content, you need to make visitors stay for a long time and spend time on the site, Google loves sites/webpages with less bounce rate.
Make sure, you distribute your content periodically on the relevant industry channels and forums.
I faced a big fear of flying, and I believe I have overcome it recently. See, going to therapists and other stupid courses is a waste of money. I was claustrophobic and I challenged myself to overcome my fear of flying and using lifts.
My first travel was to Malaysia just after the Malaysian airline went missing, lol. First of all, I was afraid of flying and my company was sending me to Malaysia for some business purpose. I was shit scared and I somehow did it with full fear in my mind.
What did I do next?
I got to know that this is going to kill my career and will not help me grow. So, I asked myself what I should do. Went to therapists and all but nothing worked out.
All they do is to help you reimagine the situation and give you some tablets for temporary relief. It doesn't help.
So what you should do?
Start small, I started taking small flights like 30 mins flights then 45 mins flights and then took a long flight of 3 hours. You might ask me how it helped? Taking small flights will help you realize what are the threats and what your mind is thinking while flying.
See, it is natural, many flyers in an airplane will be scared and that is true but that doesn't mean there is a harm and something is going to happen.
Some pointers that might help you,
> All you should be doing is developing an excitement pleasure instead of fearful thoughts.
> Think about the pilots and air hostesses, they might have flown like thousands of times.
> Pilots are so well trained and he/she is not any regular truck driver or a bus driver. They are good at what they do and they will have a good track record.
> Think about the celebrities, I believe most of the times they will be in the air.
> I think about all the good things I am going to see after reaching my destination.
> Talk to yourself, the positive affirmations. Like 'I know I am scared but I am going to do it'
> Learn how an airplane flies, there are many videos on YouTube and what get familiar with things like turbulence. Turbulence is just a slight in-comfort you experience while flying but is nothing to be worried about.
> Get a friend along on your next flight, you will feel good.
> Don't think much, just let it be. One or the other day you have to do it.
> Listen to music and motivational talks on your phone, if that helps you.
> Next time when you take a flight, talk to the flight air hostess or pilot. Talk about your fear of the flying, they will help you out.
That is it. Take small steps and that should help you.
We are all going to die one day, why think so much? Just do it. Lol, you should also see the live plane status of how many are flying above currently, you will be amazed.
Some say that Go is a relatively simple language compared to Rust. The design of both does require comprehending certain language constructs that exist in other languages. It's not really a fair comparison. The two languages do not play to the same niches and appeal for the same audience.
There are places where using Rust and Go is not a meaningful option. Rust is special because it allows for manual memory management, safely. Go has garbage collection everywhere. So for a bunch of low-level uses (hard realtime systems, OS work, web browsers) Go is simply not an option. it also appears that Rust is greatly influenced by functional programming, while Go is imperative by nature.
Go was created at Google, a company which manages a large software empire with many products. Whereas Rust, on the other hand, was created by Mozilla, a group which focuses on a few projects, and who's largely been using Rust for a single project that doesn't even encompass an entire program. I believe, end of the day they both have their own advantages and disadvantages and it is upto the individual how he uses them.
Maybe relatable, Even we believe mono repos are the right choice for teams that want to ship code faster. There are concerns that this doesn't scale well, but these are largely unfounded. Companies like Twitter, Google, Facebook run massive monolithic repos with 1000s of developers.
With mono repos you will have,
> Better developer testing: Developers can easily run the entire platform on their machine and this helps them understand all services and how they work together. This has led our developers to find more bugs locally before even sending a pull request.
> Reduced code complexity: Senior engineers can easily enforce standardization across all services since it is easy to keep track of pull requests and changes happening across the repository.
> Effective code reviews: Most developers now understand the end to end platform leading to more bugs being identified and fixed at the code review stage.
> Sharing of common components: Developers have a view of what is happening across all services and can effectively carve out common components. Over a few weeks, we actually found that the code for each microservice became smaller, as a lot of common functionality was identified and shared across services.
> Easy refactoring: Any time we want to rename something, refactoring is as simple as running a grep command. Restructuring is also easier as everything is neatly in one place and easier to understand.
What about when we are playing games online?
See what I believe is, we can apply this concept to everything in life. When you watch someone singing, if you know the song lyrics then you try to sing along in your head. So yes, it is about the way our subconscious mind works.
It is something like this quote,
"If you think you are beaten, you are
If you think you dare not, you don't
If you want to win but think, you won't
it is almost a cinch you won't."
Your mind acts according to you, and it is all about your involvement.
I believe TechinAsis publication is famous for such things. You might find something there. I read a lot of Asian tech news on this platform and it is basically for such news. Hope it helps.
Perfect! We at Shippable moved from NoSQL MongoDB to PostgreSQL for several reasons. Here is a small story,
It started with small problems...
Even though we had the ability to add features at a lightening pace, we started seeing occasional downtimes which always seemed to come down to MongoDB. For instance:
> We were very happy to have 24x7 availability with primary and secondary instances of MongoDB. However, our perf suddenly deteriorated one day and retrieval started taking more than a second per document. We tried using many tools and profilers, but could not figure out what was happening. Finally, we rebuilt a new server, switched that over as primary, and rebuilt our secondary. Retrieval times dropped to 150ms again. This is still an unsolved mystery!
> Our Mongo instance reached 4TB and we were proud of our growing adoption. Due to the lack of tooling around managing large DBs, we relied on indexes to keep the search times low. When NoSQL DBs first became popular, there was no way to create uniqueness, so these features were built as an afterthought. Some of the bloating of our MongoDB was actually due to indexes, but rebuilding them was primitive and the entire DB would lock down.
> At one point, we needed to reboot our DB server and it took MongoDB 4 hours to come back online. This led to an extended downtime for our service, and we had very little visibility into the MongoDB process or status.
And then came the knockout punch!
The biggest advantage, and disadvantage, of MongoDB is that it has a flexible schema. This means that documents in the same collection (aka table in the old world) do not need to have the same set of fields or structure, and common fields in a collection's documents may hold different types of data. In a nutshell, there are no strict schema rules and this opens it up to a lot of cowboy tinkering.
While many developers love the flexibility, it also puts a very high degree of responsibility on their shoulders to get things right.
All software architects are just going gaga over this Microservices architecture. Microservices architecture is not for everyone. You need to consider a lot of factors before adopting this model in your system and organization.
Everybody is only talking about the positive aspects of moving to microservices.
Ask yourself, do you really need microservices architecture?
To find out, you should ask yourself these questions:
How independent do you want your services to be?
How well your code is organized? Mono repo or multiple repositories?
How much operational complexity can your team handle?
Do you have a Continuous Delivery platform in place?
How is your team organized? Do they have knowledge about different toolsets and microservices architecture?
Then focus on the existing case studies like this and make an architectural strategy.
This is what we call security issues? Cloud is such a thing that anything can happen. That's the reason we are talking about shifting security to the left as much as possible, whether it is DevOps, Cryptocurrency or anything other.