Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "new venture"
-
There is this salesman right across from me that always brags about how rich his parents are and how lucky us tech guys are for having such an easy job. He told me one day that he was going to quit and make his own software company currently having no developing experience at all because "I've seen some of these developers. If those guys can do it, it'll be a breeze." I convinced him that the best language to learn in order to make your own websites/apps is Linux command line. Hilariously enough, the other 2 devs heard me say that and when Glenn the sales douche followed up with them one of them told him "Yeah, If you think you're really going to be quick with it then Linux will be your best bet, but if you have trouble just learn C++ instead and you'll still be able to make websites." Best of luck on your new Venture, you spoiled jizz stain.8
-
Most of things I'm about to say are experienced by almost 99% of developers in Africa including my country so I'm going to make it a more general rant.
As an African developer, life is both exciting and frustrating at the same time. Some of the challenges that make life difficult for developers in Africa include:
1). Slow Internet Speed: The internet in Africa can be extremely slow and unreliable, making it frustrating to work on projects that require large file downloads. This is a serious challenge for freelance developers who work from home.
2). Unstable Electricity: Frequent power outages due to inadequate infrastructure, insufficient investment in energy production and distribution, and political instability makes it difficult for developers in Africa to work consistently. Most times I get frustrated because you can experience black out at anytime of the day which could last for hours to days automatically rendering you useless if you have no power backup generator at home.
3). Low Pay: While the opportunities for software developers in Africa are quite high, the salary is often disappointing. Many talented programmers end up seeking better opportunities overseas. In fact I quit my full-time job because of this reason.
4). Lack of Support for Tech Start-ups: There are few venture capital firms in Africa willing to invest in new ideas, which makes it difficult for tech start-ups to get off the ground. It's just sad, you can have an idea and just die with it.
So in summary, it's not a walk in the park to be a developer in Africa, but despite all of that I am glad to be a part of the African journey, having the opportunity to had work at a tech agency firm on various projects ranging from healthcare to finance, I find it rewarding to know that my work has contributed to a better future for my continent. 🤞6 -
There are a couple of them to list! But to sum my main ones(biggest personal heroes):
John McCarthy, one of the founding fathers of Artificial Intelligence and accredited with coining such term(sometimes before 1960 if memory serves right), a mathematical prodigy, the man based the original model of the Lisp programming language in lambda calculus. Many modern concepts that we have in programming where implemented in one way or another from his systems back in the day, and as a data analyst and ML nut.....well I am a big fan.
Herb Sutter: C++ programmer extraordinaire. I appreciate him more for his lectures and published articles than anything else. Incredibly smart and down to earth and manages to make C++ less intimidating while still approaching it with respect.
Rich Hickey: The mastermind behind Clojure, the Lisp dialect for the JVM. Rich is really talented and his lectures behind his motivations and reasons behind everything he does with Clojure are fascinating to see.
Ryan Dahl: Awww shit y'all know how it is. The man changed web development both in the backend and the frontend for good. The concept of people writing their own servers to run their pages was not new, but the Node JS runtime environment made it more widely available to people by means of a simple to use language that was already popular with web developers. I would venture to say that Ryan's amazing contributions to JS made the language better, as it stands, the language continues to evolve and new features that make it overall better keep being added. He is currently building Deno, which would be a runtime environment for TypeScript, in Rust.
Anders Hejlsberg: This dude was everywhere man....the original author of Turbo Pascal and the lead of Delphi back in the day. These RAD tools paved the way for what would be a revolution in the computing world. The dude is also the lead architect and designer of the C# programming language as well as TypeScript.
This fucker is everywhere and I love it.
Yukihiro "Matz" Matsumoto: Matsumoto san is the creator of the Ruby programming language. Not only am I a die hard fan of Ruby, but of the core philosophies that the man keeps as the core of his language design: Make the developer happy, principle of least surprise. Also I follow: minswan which is a term made by the Ruby community that states Mats is nice so we are nice. <---- because being cool to others is better than being a passive aggressive cunt.
Steve Wozniak: I feel as if the man does not get enough recognition...the man designed the Apple || computer which (regardless of how much most of y'all bitch and whine) paved the way for modern micro computers. Dude is also accredited with designing one of the first programmable universal remotes(which momma said was shitty) but he did none the less.
Alan Kay: Developed Smalltalk and the original OOP way of doing things. Smalltalk as a concept is really fucking interesting. If you guys ever get the chance, play with Pharo, which is a modern Smalltalk. The thing is really interesting and the overall idea of Smalltalk can be grasped in very little time. It sucks because the software scales beautifully in terms of project building, the idea of hoisting a program as its own runtime environment and ide by preserving state through images is just mind blowing to me. Makes file based programs feel....well....quaint.
Those are some of the biggest dudes for me. I know that the list is large, but I wanted to give credit to the people that inspired me the most. Honorary mention goes to other language creators and engineers of course, but it would be way too large to list!9 -
I got my dirty fingers on this leak of an AMAZING ML model capable of pondering EVERY PARAMETER IN THE UNIVERSE and saying if your business idea needs improvement or is good to go.
BEHOLD THIS 100% PURE PYTHON SOLUTION:
```python
import random
def magic(*args, **kwargs):
if random.random() > 0.5:
return "Good to go!"
else:
return "Requires improvement on value proposition"
```
This LEAK is from a startup that just received 4 BILLION USD IN VENTURE CAPITAL to improve their AI SYSTEMS.
Literally enough money to solve world hunger forever.
Who else is gonna invest in NEW THERANOS ADVANCED A.I. RESEARCH INTERNATIONAL INC?8 -
Back on dev rant, been a while. Been two Jobs later...
Was extremely underpaid at the previous job.
Started a new venture two weeks ago. Long story short this company outsources their developers to other companies. The job I applied for is 'Junior Developer'. JUNIOR DEVELOPER!!!
Yet I'm being outsourced as an 'Intermediate Developer'.
Honestly I like the challenge, but businesses need to treat their employee's properly and not manipulate their young developers so they can get more money for cheap.
Really now, I've been dealing with this everywhere I go and it pisses me off.
On top of that I have no Senior Developer. I am the only developer. The other six, including my boss, are DBA's and don't know C#1 -
I don't care about market cap. Stick your hype-driven business practices up your ass. Infinite growth doesn't exist. I won't read your fucking books and attend your fucking bootcamps and MBAs. You don't have a business model. Selling data is not a business model. Fuck your quick-flip venture capital schemes, and especially fuck your “ethics”.
I will be the first alt-tech CEO. I only care about revenue. The real money, not capitalization bubble vaporware. You don't need a huge fleet of engineers if you're smart about your technology, know how to do architecture, and you're not a feature creep. You don't need venture capital if you don't need a huge fleet of engineers. You don't need to sell data if you don't need venture capital. See? See the pattern here?
My experience allows me to build products on entirely my own. I am fully aware of the limitations of being alone, and they only inspire lean thinking and great architectural decisions. If you know throwing capacity at a problem is not an option, you start thinking differently. And if you don't need to hire anyone, it is very easy to turn a profit and make it sustainable.
If you don't follow the path of tech vaporware, you won't have the problems of tech vaporware, namely distrust of your user base, shitty updates that break everything, and of course “oops, they raised capital, time to leave before things go south”.
A friend of mine went the path I'm talking about, developed a product over the course of four years all alone, reached $10k MRR and sold for $0.8M. But I won't sell. I only care about revenue. If I get to $10k MRR, I will most likely stop doing new features and focus on fixing all the bugs there are and improving performance. This and security patches. Maybe an occasional facelift. That's it. Some products are valued because they don't change, like Sublime Text. The utility tool you can rely on. This is my scheme, this is what I want to do in life. A best-kept secret.
Imagine 100 million users that hate my product but use it because there are no alternatives, 100 people in data enrichment department alone, a billion dollars of evaluation (without being profitable), 10 million twitter followers, and ten VC firms telling me what to do and what data to sell.
Fuck that. I'd rather have one thousand loyal customers and $10k MRR. I'm different, some call it a mental illness, but the bottom line is, my goals are beyond their understanding. They call me crazy. I won't say it was never about the money, of course it was, but inflating your evaluation is not “money”. But the only thing they have is their terrible hustle culture lives and some VC street wisdom, meanwhile I HAVE products, it is on record on my PH. I have POTDs, I have a fucking Golden Kitty nomination on health and fitness for a product I made in one day. Fuck you.7 -
In the mid-2010s, we barely had any apps in our native language and popular coupon and review sites were lackluster in our neck of the woods.
So me and some old uni colleagues got together to make a WhatsApp based "wtf is going on right now and right around here"
think Groupon meets yelp meets Google maps meet trending topics. The idea was that local business would post deals and events and people would comment on it giving stars on real time, with geolocation. So you could see what was going on right next to you, and business owners only needed WhatsApp installed to post new topics.
We... failed to go viral. That simple. Things get frustrating when infinite no-questions-asked venture capital is not available.
Then me and the other founders got very lucrative jobs in former British colonies and that was it.
This idea might still work nowadays, but it would be reeeealy hard to navigate around Whatsapp's terms of service.
Good luck to anyone who might want to try.3 -
Happy 2023, may all your gym memberships be worth while, this time🙃
On a serious note though, what's your goto blogging platform these days?
Beyond Wordpress because well, let's not trigger PTSD for some of us, what are you gals and guys using in 2023?4 -
Any technical cofounders here? I've been offered to be a technical co-founder for a new venture. This is a venture that has the same founding team as the startup I'm working with for last 3 years or so. The current venture may be acquired in the near future with the founding team exiting.
Now my question (s) are these:
1. I know the team. We're friendly. But until now the relationship has been that of an employer-employee. What all should i consider before taking this up?
2. Since founders generally take up salaries only what is required for them to sustain. It would mean a financial cut for me too. So I'm stuck in the dilemma of moving towards an entrepreneurial route vs if it fails and I've to work again i may have to start off with a lower salary in the future.
I'm a risk taker (some call it seeker) when it comes to that. Looking forward for some helpful suggestions.question startups start-up startup hell suggestions are welcome suggestion startup suggestions founders founder technical co-founder co-founder3 -
Next time you think you’re failing at a new open source venture, remember the stories of your UNIX ancestors (eunuchs ancestors?) ;)
Unix at 50: How the OS that powered smartphones started from failure
Today, Unix powers iOS and Android—its legend begins with a gator and a trio of researchers.
https://arstechnica.com/gadgets/...2 -
Broadly there are two things which concerns me:
1: Clients' businesses fail miserably or change their direction.
2: Instead of focusing and improving the quality of their work/product, they prioritise remaining things instead.
BONUS: Don't forget those individuals who dream really big but fails to take any action towards it, just talking. I stay away from these people personally.
Because of these reasons design gets vanished or no longer valid for their new business venture, and don't forget the time and dedication it took to create, as a freelancer it hurts a bit.
I like working for non-profit organisations, most of them look for volunteers. Your work and efforts are alive, and you have to be jack of all trades IMO when dealing with them. Additionally in the process you will meet some extraordinary individuals. -
A bit late.. and not much about how to learn to code..but more of a figuring out if the kid has a right mind set to do so..
If the kid is not the type to question everything, not resourceful, not a logical/critical thinker, gives up easily and especially if not interested in how things work then being a dev is most probably not for them.. they can still persue coding, but it will end badly..
From my experience, people who have a better education than me, but lack those skills turned out to be a crappy dev.. not interested in the best tool to complete the tasks, just making 'something', adding more shit to the already shitty stack.. and being happy with that.. which of course is not the best way to do things around here..or in life!!
Soo.. if the kid shows all that and most importantly shows interest in learning to code.. throw him the java ultimate edition book and see what happens.. joke!
There are plenty of apps thath can get you started (tried mimo, but being devs yourself it's probably not so hard to check some out and weed out the bad ones) that explain simple logic and syntax.. there is w3schools that explains basics quite well and lets you tinker online with js and python..
so maybe show them these and see what happens.. If it will pick their interest, they will soon start to ask the right questions.. and you can go from there..
If the kids are not the 'evil spawns' of already dev parents or don't have crazy dev aunties and uncles, then they will have to work things out themselves or ask friends... or seek help online (the resourceful part comes here).. so google or any flavour of search engines is their friend..
Just hope they don't venture to stack overflow too soon or they will want to kill themselves /* a little joke, but also a bit true.. */
Anyhow, if the kid is exhibiting 'dev traits' it is not even a question how to introduce it to the coding.. they will find a way.. if not, do not force them to learn coding "because it's in and makes you a lot of moneyz"..
As with other things in life, do not force kids to do anything that you think will be best for them.. Point them in direction, show them how it might be fun and usefull, a little nudge in the right direction.. but do not force.. ever!!!
And also another thing to consider.. most of the documentation and code is written in english.. If they are not proficient, they will have a hard time learning, checking docs, finding answers.. so make sure they learn english first!!
Not just for coding, knowing english will help them in life in general. So maaaaybe force them to learn this a bit..
One day my husband came to me and asked me how he can learn.. and if it's too late for him to learn coding.. that he found some app and if I can take a look and tell him what I think, if it is an ok app to learn..
I was both flattered and stumped at the same time..
Explained to him that in my view, he is a bit old to start now, at least to be competitive on the market and to do this for a living, but if it interests him for som personal projects, why not.. you're never too old to start learning and finding a new hobby..
Anyhow, I've pointed out to him that he will have to better his english in order to be able to find the answers to questions and potential problems.. and that I'm happy to help where and when I can, but most of the job will be on him.
So yeah, showed him some tutorials, explained things a bit.. he soon lost interest after a week and was mindblown how I can do this every day..
And I think this is really how you should introduce coding to kids.. show them some easy tutorials, explain simple logic to them.. see how they react.. if they pick it up easily, show them something more advanced.. if they lose interest, let them be.
To sum up:
- check first if they really want to learn this or this is something they're forced to do (if latter everything you say is a waste of everybodys time)
- english is important
- asking questions (& questioning the code) is mandatory so don't be afraid to ask for help
- admitting not knowing something is the first step to learning
- learn to 'google' & weed out the crap
- documentation is your friend
- comments & docs sometimes lie, so use the force (go check the source)
- once you learn the basics its just a matter of language flavour..adjust some logic here, some sintax there..
- if you're stuck with a problem, try to see it from a different angle
- debugging is part of coder life, learn to 'love' it4 -
I don't have any experience in teaching, but I'd venture to say that teaching anything is hard. For most subjects, teaching has been refined over thousands of years to be easier and meaningful. Not CS. As has been mentioned by many people CS is a very new subject when compared to the likes of maths, for example, and education systems haven't been able to cope with it adequately (nor should they be expected to).
That the CS industry is rapidly evolving certainly doesn't help matters, but in reality that shouldn't really be that big of a problem (at least in earlier years of education). The basics of computer systems and programming don't really change that much (please correct me if I'm wrong) and logic stays the same. Even if you learn stuff that's a bit out of date it can still be useful and good lessons should be able to be applied to new technologies and ideas.
Broken computers is a big inconvenience, but a lot of very useful things can be done without a computer, and I should think the situation is a lot better than it was 5 years ago. What I think would be good, instead of trying to use broken computers would be to get students to set up and use a raspberry pi each; you learn about something other than windows, learn how to install an OS and you don't need that much computing power for teaching people computer science.
I think the main problem is a lack of inspiring teachers. Only a very few teachers will be unable to get you through the exams if you put in the effort, but quite a lot of the time students don't put in the effort because they can blame it on the teacher.
My solution would be to try and get as many students into computer science as possible and the rest will follow: more people will become teachers, more will be invested in the subject, more attention will be payed to the curriculum.
That's not to say I don't agree that many of the problems that have been mentioned need to be fixed for CS education to work properly, just that there is no way that I can see to fix them currently without either creating more problems or some very rich person giving a load of money.
This has gone on a lot longer than I expected so I'll stop now.14 -
I can't help but stress out about finding work in development. I just want an internship / entry level summer position to put myself in a better position for post college and to explore and learn in new environments. But it seems like my best chance for scoring that internship is building a solid portfolio or experience, something that I haven't had time to do..
I wrote my first line of code (that wasn't HTML or CSS) when I got to college. Since then almost all my time has gone into my cs engineering curriculum and working a real shitty blue collar job during breaks (for 4 years now) because Im broke and got denied by the 20+ positions I applied for. I can't really do anything with the code I wrote for my schoolwork because I can get fucked if I post it anywhere or share it. I have loads of ideas, but am worried that they are too big to do while maintaining my GPA and scholarships. It sucks too because I am a quick learner, and would even venture to call myself good at what I do.
So since I have hardly been able to pursue any independent studies, I haven't been able to really explore the field, so I don't even know what to areas i need to focus on to make myself a better candidate. So basically I'm broke, don't have shit for pet projects, don't know what I want to do with my life, and can probably expect to work like a dog next summer too because I've heard most companies hire for the summer in the fall.
I don't write this because I feel bad for myself. I write this because it's likely that most people here have been in a similar situation. I also don't like to make excuses for myself like I have been doing. Any advice folks? What should I be doing differently?3