We’re #hiring a new Senior Full Stack Developer - Simulation in United States. Apply today or share this post with your network.
TuSimple’s Post
More Relevant Posts
-
You don't need rockstar developers. You need rockstar requirements and a band of average developers. Most of us are building really simple software. We display some data, save it to a database, call an API, etc. It's not SpaceX rocket science, self driving cars, or ChatGPT. What you need is really good requirements, some basic software architecture to follow, and a team to hammer out the features. A lot of times, the requirements/architecture are the true innovation. With good requirements, you can make a bunch of average developers look like rockstars and produce #1 hits.
To view or add a comment, sign in
-
Today's winner for Worst Take on The Internet ™. There are a couple of instructive things can be taken from it though: 1) Requirements trump development - this assumes the typical, though delusional idea that requirements are static. The reason you need master software engineers is for the very reason that requirements shift continuously. Engineers have to glean the learning rapidly, assist the team in digesting it, and move forward quickly. The better you are at this - the faster you will deliver - the faster you deliver the more value you create and the more return you reap. Tolerating mediocre developers robs your customer - and it robs you as a stakeholder in your business. 2) "We only build simple things" - maybe this is true for your organization, maybe it isn't. Either way, no matter how simple it is, it'll be built faster if your engineers have a better grasp of the craft. Stocking your team with B and C players simply because you might still get a product out of them doesn't mean you'll get the best, highest value. Again, you're robbing your customer. Don't rob your customer - hire A players.
You don't need rockstar developers. You need rockstar requirements and a band of average developers. Most of us are building really simple software. We display some data, save it to a database, call an API, etc. It's not SpaceX rocket science, self driving cars, or ChatGPT. What you need is really good requirements, some basic software architecture to follow, and a team to hammer out the features. A lot of times, the requirements/architecture are the true innovation. With good requirements, you can make a bunch of average developers look like rockstars and produce #1 hits.
To view or add a comment, sign in
-
This coming weekend is the 92nd running of the Le Mans 24 Hours, the greatest motor race in the world. One of the front-runners is #PorschePenskeMotorsport, if they win it will be Porsche AG's 20th overall victory (and their 109th class victory). It will be Team Penske's first at Le Mans, but they have 627 wins and 44 championships in other series. These companies are natural partners because both have always focused on excellence. At a race, you could eat off the floor of a Penske garage. Their cars are prepared to perfection. Porsche has always pursued excellence rather than breadth or wild innovation, for example the engine they'll be using is the third development of one they designed 20 years ago (Porsche won championships with it in the first two iterations and they are leading the championship again this year). Porsches aren't just fast at the start, they are fast at the end of 24 hours (when so many other cars are falling apart). I love racing because it's a pure test of product development. Most companies (and possibly the entire Product Management profession) prioritize doing 'more', racing shows us again and again it's excellence that wins.
You don't need rockstar developers. You need rockstar requirements and a band of average developers. Most of us are building really simple software. We display some data, save it to a database, call an API, etc. It's not SpaceX rocket science, self driving cars, or ChatGPT. What you need is really good requirements, some basic software architecture to follow, and a team to hammer out the features. A lot of times, the requirements/architecture are the true innovation. With good requirements, you can make a bunch of average developers look like rockstars and produce #1 hits.
To view or add a comment, sign in
-
What people like Matt don't seem to understand is that all industrial/financial systems that are currently in effect have an inherent propensity to be systems of exponential growth. This in turn necessitates min-max solutions meaning that industries want to maximize the juice they can squeeze out of the work-force aka maximize talent & productivity with the least amount of investment. You can't survive in this landscape just by building "simple software" all the time. It just doesn't work that way. You might find this "inconvenient" as a software engineer but you cannot solve this problem using thinking that's rooted in the same level of thinking that created the discontents of "exponential growth" in the first place.
You don't need rockstar developers. You need rockstar requirements and a band of average developers. Most of us are building really simple software. We display some data, save it to a database, call an API, etc. It's not SpaceX rocket science, self driving cars, or ChatGPT. What you need is really good requirements, some basic software architecture to follow, and a team to hammer out the features. A lot of times, the requirements/architecture are the true innovation. With good requirements, you can make a bunch of average developers look like rockstars and produce #1 hits.
To view or add a comment, sign in
-
Hey #iOSEngineers, Have you ever wondered what level you're at? With the roadmap developed by Ronan, you can better understand where your knowledge fits best. If you progress from Swift Basics to Application Life Cycle, you may be considered an entry-level software engineer. Otherwise, to be considered at level 2, you must master clean architecture, for example. Check it out below! https://lnkd.in/d_mWXztK
To view or add a comment, sign in
-
-
I work at GitHub, a Microsoft company. No cold contacts please. If I don't know you, I will probably not add you, sorry
GitHub’s hiring 4 remote SAST engineers in 🇬🇧🇩🇪 (UK and Germany) You’ll work on Code Scanning, a major part of GitHub Advanced Security, GitHub’s developer-first AppSec platform. Isa is great to work with and has lots of experience leading Engineering teams, and the Code Scanning team as a whole has a culture and skillset I enjoy working alongside (I’m not in the Engineering team, but work with them reasonably closely). Want an idea of the technologies? Here’s a few I know of: we use Copilot (powered by OpenAI LLMs) to provide autofix for SAST findings; the UI is written in Ruby. The database is MySQL. The Code Scanning GitHub Action is written in TypeScript. #hiring #GitHub #SAST #AppSec #Ruby
Do you want to join me in the mission of securing the world's software? I am looking for 4 software engineers to build code scanning, the core of our GitHub advanced security offering, where found means fixed, and now with the help of AI! The four positions are remote, and applicants can be located in the UK and Germany. https://lnkd.in/emFw5jN7 https://lnkd.in/euZfUZPH
To view or add a comment, sign in
-
Some companies need rockstar developers. Most need 𝙖 developer. The difference? It comes down to the product being built. If you are innovating something extremely cutting edge, you probably need the most talented software engineers on the planet. Building OpenAI, self driving cars, sending humans to mars, etc, requires rockstar talent. You 𝙥𝙧𝙤𝙗𝙖𝙗𝙡𝙮 think what you are building is really cutting edge. If you are querying data from a database and displaying it in a web browser... the industry has been doing that for 25+ years. Millions of developers already know how to do that with 73 different tech stacks. It's a 101 college class. Almost any developer can help you. What you really need is an amazing product vision and requirements to give that developer. That would help you more than a rockstar developer.
To view or add a comment, sign in
-
This is actual footage of a programmer dodging changing requirements, merge conflicts, bugs, tight deadlines, burnout, outdated documentation, layoffs, and then heading into the weekend. #softwareengineering #programming
To view or add a comment, sign in
-
-
The world needs 1000x or more software... Today, one key constraint is the lack of software developers. (over 500k open positions)! It's because tools used by devs are so bad, it takes SO long to build anything? Now, imagine a world where you can build at the speed of your imagination! And, imagine it's at production-worthy scale, resilience, redundancy, etc. That's the world we're building with Canopy! #compose #codeless
To view or add a comment, sign in
-
Kforce keeps a close eye on the local SLC technology labor market, generating informative data insights for our clients. In the Greater SLC area, which companies have the largest front-end and full-stack engineering teams? 1- Adobe 2- Goldman Sachs 3- Lucid Software How many unique companies in Utah employ front-end and full-stack engineers? 742 In later posts, I'll be sharing some interesting results from our Utah tech market compensation analysis; like - Why does the median compensation jump dramatically between 2 and 3 years of experience, but only for certain software engineering skills?
To view or add a comment, sign in