Earlier quoted context omitted.
You should do everyone a solid and name-and-shame the frontend/MySQL company because dear God that's horrifying.
They don’t exist anymore, they didn’t have what it takes :O
And nothing of value was lost
I Don’t Believe in Full-Stack Engineering
91–100 of 199 posts
Re: I Don’t Believe in Full-Stack Engineering
#92I once met a software engineer who said I was not full-stack because I didn't know how to add to the Linux Kernal. I once met a hiring manager who said I'm not front-end because I don't know how to vertically shard MySQL and "every front-end developer knows how to do that." Technology stacks differ per company and the definition of the title will also differ. That doesn't mean it doesn't exist.
If you can't make your own transistors to speed up the UI, then you're not full-stack... and no one is.
Re: I Don’t Believe in Full-Stack Engineering
#93This is a weird rant. He is complaining that someone who does many things won't be as good in front-end as someone who does only front end. ...ok? Nobody expects full stack engineer to be all that great in front-end. That's why he is not a front end engineer. Vice versa he won't probably be all that good in SQL or in administration and devops. I am not even sure what is this guy complaining about exactly
Disagree. I expect full-stack developers to be _great_ at frontend, and _capable enough_ to build the backend. When resources are constrained you want the customer-facing side of the product to be a priority.
> _great_ at frontend, and _capable enough_ to build the backend
I think that bias says more about the particular kind of company you're in than the general label of "full-stack".
Re: I Don’t Believe in Full-Stack Engineering
#94I once met a software engineer who said I was not full-stack because I didn't know how to add to the Linux Kernal. I once met a hiring manager who said I'm not front-end because I don't know how to vertically shard MySQL and "every front-end developer knows how to do that." Technology stacks differ per company and the definition of the title will also differ. That doesn't mean it doesn't exist.
"Fullstack is more what you’d call ‘guidelines’ than actual rules."
Re: I Don’t Believe in Full-Stack Engineering
#95I'm the only competent developer in our company. So believe it or not, but I'm doing it all, from tinkering in disassembled Oracle 9i JDBC driver, to planning Oracle migration to writing SQL queries, reverse-engineering stored procedures, modifying Delphi sources, writing Java code, writing Kotlin code, writing HTML, JavaScript, CSS, Objective C, rolling out some tiny PHP website, writing brute-forcer to crack P12 pr…
How was your day at work?
> writing brute-forcer to crack P12 private key because someone forgot password
LOL
Re: I Don’t Believe in Full-Stack Engineering
#96> Of all the engineers I’ve met over the years only one has come close to what that title, full-stack engineer, implies: the ability to easily navigate the back-end and front-end with a senior level of expertise.
In the first paragraph, the author sets up a really weak straw man for himself to defeat. If you define "full-stack engineer" as "an expert at front and back end", it's pretty easy to not believe in it since you may as well be restricting the category to people who are 3σ. If you define "full-stack engineer" as someone who "can do front and back end moderately well". This is much easier to believe in.
Re: I Don’t Believe in Full-Stack Engineering
#97This article is conflating junior developers with full-stack engineering. I work on the entire stack. Can I work with databases and write queries? Sure. Can I do it as well as a data architect? No. That's not what's expected of a full stack engineer. We can have meaningful, productive discussions with everyone on all parts of the stack. We'll talk with the data architect, write/tweak a query if we need to, we'll talk…
Agreed. I would also add, I don't think frontend vs backend accurately describes how skillsets are clustered anymore -- especially with JavaScript's increasing ubiquity. I would cluster skillsets into: ops, development, and design. Ops: making things highly available, logging, performance monitoring, reliability, deployment scripts Development: Writing code on both frontend and backend. Design: Visual design and CSS/…
[deleted]
Re: I Don’t Believe in Full-Stack Engineering
#98He attributes bad web sites to lack of skills. I'm sorry, but in my experience it generally is due to lack of time and budget , no matter how experienced you are. Experience helps a lot but not every site is worth pouring in the money required to make it top notch. Some times meeting business needs matters more than technical perfection.
It also often results from lack of clarity in communication about things like
* Why are we doing this?
* What is the business value we expect from this?
* What resources do we need to do this to a level of quality where it has that business value?
Re: I Don’t Believe in Full-Stack Engineering
#99"Front-end development is important today and it will be important in twenty years’ time, it’s not going away anytime soon." That I don't think will be true unless it's pertaining the eventual abandonment of the web browser as the run-time. The awful tangled spaghetti that is the current code for a web site UI is not tractable going forward. It takes way too much effort to make a usable interface for the value in ret…
> What I do know is the advancement of computing is being hindered by the lack of a competent UI system.
Hasn't that always been the case? UI has always been a mess, at least as far back as I can remember.
Re: I Don’t Believe in Full-Stack Engineering
#100I'm the only competent developer in our company. So believe it or not, but I'm doing it all, from tinkering in disassembled Oracle 9i JDBC driver, to planning Oracle migration to writing SQL queries, reverse-engineering stored procedures, modifying Delphi sources, writing Java code, writing Kotlin code, writing HTML, JavaScript, CSS, Objective C, rolling out some tiny PHP website, writing brute-forcer to crack P12 pr…
How many developers are there at your company?
Oh... it's just her/him :-P