Joined devRant on 10/21/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
1. Have some issue with my code which spits out cryptic compiler error.
2. Ask on stack overflow, Reddit, etc for a solution.
3. Get scolded at for "not reading the documentation" and "asking questions which could be answered by just Googling". Still no clue what I'm doing wrong, or what the solution would be.
4. Find someone else's vaguely related problem.
5. Post my problematic code as the answer, with arrogant comment about OP being a retard for not figuring that out for themselves.
6. A dozen angry toxic nerds flock in to tell me how retarded and wrong I am, correcting me... solving my original problem.
7. Evil plan succeeded, my code compiles, and as a bonus I made the internet a worse place in the process.
I think if you tell a bunch of autistic neckbeards that "all coronaviruses are fundamentally incurable", you'd have a vaccine within a week.16
Freelance web developers: please talk about yourselves.
How much experience did you have at the beginning?
How did you get started and was it much work to get set up?
How do you find a constant stream of clients?
Do you make a living wage just from your freelance work?
Any other information you'd like to share is appreciated.18
IF LIVES DEPEND ON A SYSTEM
1. Code review, collaboration, and knowledge sharing (each hour of code review saves 33 hours of maintenance)
2. TDD (40% — 80% reduction in production bug density)
3. Daily continuous integration (large code merges are a major source of bugs)
4. Minimize developer interruptions (an interrupted task takes twice as long and contains twice as many defects)
5. Linting (catches many typo and undefined variable bugs that static types could catch, as well as a host of stylistic issues that correlate with bug creation, such as accidentally assigning when you meant to compare)
6. Reduce complexity & improve modularity -- complex code is harder to understand, test, and maintain
It's only day one of the year and I'm already pissed right off
Why the fuck do all clients expect you to come up with absolutely everything!?
All I ever get is we want a website. I ask well what do you want on it.. our products .. news? Contact maybe ... Urm our business information ... That kind of stuff.
Well what are they?
Pft.. I here is a name if our products. And other stuff
WE ARE SELLING IT WAT ARE THE PRICES AND INFORMATION DO YOU HAVE IMAGES
Yeah do you want them
Of course I do 😐
Great here's 2 of them we have 1100 so I'll get more to you soon.
😤 Thank you!
Holy shit it's always like talking to a fucking brick wall.. why do people have to make our jobs so hard it's already fucking tough
I have no time to plan your entire website by myself I don't know what you want on it. How could I possibly know that!? It's your fucking site10
This is the most hilarious stackoverflow rant ever, quote:
"Strong cryptography only means the passwords must be encrypted while the user is inputting them but then they should be moved to a recoverable format for later use."
Petition to officially rename the term 'build' to 'kraken', so QA can shout 'Release the Kraken' and I can shout back 'The Kraken has been released!'.19
Just released my JS devRant API wrapper. It has support for posting, viewing, voting and much more. If you are interested here is the NPM package:
For my passionate coders out here, I have some tips I learned over the years in a business/IT environment.
1) Don't let stupid management force you into making decisions that will provide a bad product. Tell them your opinion and why you should do it that way. Never just go with their decision.
2)F@#k hackathons, you're basicly coding software for free, that the company might use. Want to probe yourself? Join a community and participate in their challenges.
3)No matter how good you are, haters are common.
4)Learn to have a good communication, some keywords are important to express yourself to other developers or customers. Try crazy things, don't be shy.
5)Never stand still, go hear at other companies what they offer, compare and choose your best fit. This leads me into point...
6)if you've been working for over a year and feel that you have participated enough in the companies growth, ask a raise, don't be afraid...you're wanted on the market, so either they negotiate a new contract or you find another job.
I'm sharing these with you as I made many mistakes regarding these points, I have coded for free or invested so much time in a company just to prove myself. But at the end I realize that my portfolio is enough to prove that I'm capable of doing the job. They don't like me? Or ask me stupid questions that I can google in 5 minutes. I'll just decline the job and get something better. Companies end up giving me nothing in return compared to the work I have put into it. At the end after some struggles you'll find a good fit and that's so important for your programming career. Burnouts happen quite often if you're just a coding puppy.
If some of you still have additional tips be sure to post them under here11
UPDATE: devRant Trans-Oceanic Journey Community Project
It was a mere 12 days ago that I asked the question; 'Could devRanters, as a community, build a 21st Century Technology-Laden ‘devRant devie-Stressball-in-a-Bottle’ and send it on a journey across the Atlantic ocean?
I am thrilled to report that devRanters enthusiastically accepted this difficult challenge. A core team quickly formed and a tremendous amount of research and progress has been made in a short period of time. I want to give you a high level-flavor of what we are doing. Please keep in mind we still need your help. We welcome all develops to take part in this journey.
I want to give appreciation to the devRant Founders @dfox and @trogus. Without your support and sponsorship this project would not have been possible. devRant brought us together and it a reality. Devie journeying across the Ocean the Columbus sailed will stir the imagination of children and adults worldwide when we launch on May 1, 2017.
Some of the research and action items in progress:
- Slack and trello environments were created to capture research and foster discussion.
- A Stony Brook University Oceanography Professor suggested the Gulf Stream would be a good pathway across the ocean. We researched it very and agree. The Gulf Stream has been a trans-Atlantic conduit for hundreds of years. We are deciding whether to launch from Cape Hatteras, NC or the Virginia coast. Both have easy access to the rapid currents in the Gulf Stream.
- We are researching every detail of the Gulf Stream to make the journey easier and faster for devie. We have maps and a team member gathered valuable ideas reading a thorough book – ‘The Gulf Stream’.
- We decided on using a highly resilient plastic rather than glass for the bottle material. Plastic is much lighter, faster and glass breaks down more easily. The lightweight enclosure will allow us to take full advantage of waves and ample trade winds. We are still discussing the final design as we want to minimize friction and mimic the non-locomotion fish that migrate thousands of miles riding the Gulf Stream.
-The enclosure might be 3D printed unless we can locate a commercial solution. We have 3D specs and are speaking with some experts. There are advantages and dis-advantages to each solution.
- We will be using Iridiums' RockBLOCK two-way satellite technology to bounce lat-long coordinate pings off their 36 low-orbit satellites. The data will be analyzed by our devRant devie analysis software. IOS and Android public apps being built by the team will display devie's location throughout the journey in.
- Arduino will be used as the brains
- Multiple sensors including temperature and depth are being considered
-A project plan will be published to the team Friday 12/9. Sorry I am a few days late but adding some new ideas.
There are still a lot of challenges we must overcome and we will.
That’s all for now. I will send updates and all ideas / comments are valued.6
My guide to know if your startup is failing:
My Qualifications: Every startup I've joined has failed. Not necessarily because of me.
For the sake of me typing faster, x=startup.
1) X doesn't have a product, but just an idea that x keeps pitching as the next "big thing". (What's with this shit anyway?)
2)X keeps changing products, One day your designing IoT sex toys and the next day your building a self aware AI. For some reason, the people at X saw Silicon Valley or that meme about how Instagram was created and thought "Fuck that happens to every moron who can switch on a computer."
3) Even worse, X keeps changing industries.
4) X keeps lying to you, your marginal user base and seems overall unethical. (You should leave at this point.)
5) X wants to target some obscure and very specific market and keeps pitching the company along the following lines
<famous_company> for <random_market>
Eg: "Yo bro it's like Amazon but for necrophiles."
6)X keeps saying that X is the next big thing. (X is not and I can't emphasize this point enough.)
What you should realize is this is my general observation and some or all of these points may not apply to every situation.
Sorry for typos and any other stuff.11
Spend enogh time planning, before you start coding
Write maintanable code
Join the local gym and exercise regulary, it will keep you happy and prevent early burnout
Stop fooling yourself by thinking that the hurry & pressure will eventually go away if you work overtime & stretch yourself to heroics weekly. They won't, and they never will (and even shouldn't). Focus on building sustainable habits that propel you towards your goals day by day, and don't give up until you're where you want to be. Period.2
It has to be the community. Just look at devRant - an open community where - unlike on the rest of the internet - people are friendly and warm. Then there's the concept of open source and GitHub, where people post large and complex projects for free and even the smallest of developers can create issues and pull requests (shouldn't they be called push requests though?) - no other profession will help others out in over 15 million different ways.5