#REDDIT IS SOFTWARE PRO WORLD LEGIT CODE#
#REDDIT IS SOFTWARE PRO WORLD LEGIT PROFESSIONAL#

When it comes time to solve the problem at the next level, the Lego stuff can be less helpful than it looks even as a prototype, as even at small scales a lot of the engineering in the Lego was solving around the limitations of Lego in the first place, rather than solving the problem per se.Дў. You can only do what there's Lego bricks for. The solutions may work, but they aren't really that good. However, you end up with two sorts of problems if you start letting people just build solutions to whatever they like with Lego:ДЎ. It can be fast & effective, it's certainly easy, especially if you imagine we've abstracted away the question of what bricks you have so you have as many as you need of any kind & color. You can build interesting and useful things out of Lego, more than you may even realize. I think there's an interesting analogy to be drawn with Lego. I jest, but sometimes it feels like that would be just as helpful and fulfilling. I made a joke recently that in companies that have a formalized promotion process, if you apply for promotion and are denied, one of the consolation prizes should be that you get to apply for someone else to be demoted. > I don't think i'm being _underpaid_ for my architect + dev hat, but i do wonder if someone else is also being paid for architect but i'm cleaning up for them lol. pick your favorite Fortune 500 company and their cloud provider, security engagements, hardware vendors etc. They can collect what I believe are reasonable salaries and just route between the engineers on the customer side who actually know what they want, and engineers on the provider side who can actually provide it.ДЄny giant coupling between an application and platform ends up looking like this, I.e. There are lots of places for semi technical people who sort of know what theyвЂ™re doing, but donвЂ™t really provide value, to hang out in a large and growing enterprise sales org. Probably, depending on the size of the org. > the positions we have that more traditionally handle a more complete design. I don't feel it's unique, but maybe it's just how i put myself out there. I dunno, all the companies i've been at have been like this. Worse yet i wouldn't have the ability to shape the UX for better performance. If they laid everything out perfectly i'd be left with just writing the correct design patterns in code, using the right data structures, etc. I use quotes because i also get paid much more than the other devs i speak of, so i go back to what i said earlier, i think i get paid for this. I suspect this is because they expect/trust me to follow through, and i do - but this also effectively takes 'advantage' of what i offer. I notice they give me a far more loose definition than they give less experienced devs. I've also found that the designers seem to. are they being overpaid in our org? I don't think i'm being _underpaid_ for my architect + dev hat, but i do wonder if someone else is also being paid for architect but i'm cleaning up for them lol.

The bigger question to me is if the positions we have that more traditionally handle a more complete design. To be the architect of their general direction. They wanted someone (well, a team of devs) to deal with this stuff. However i legitimately think that is what they hired for. When i have to point out drastic UX flaws or impossibilities it is definitely frustrating. I'm in a smaller org and yea, the product team definitely skimps on plenty of details. i don't mind the design process (or lack there of) you describe.

#REDDIT IS SOFTWARE PRO WORLD LEGIT PROFESSIONAL#

I don't hold this against any of my clients, it's ok if they don't quite know what they want, I'm the professional and it's my job to figure that out. They will say something like 'Oh pinterest, instagram, facebook, etc have something like this', we pull up that site and they show me, and from there I adjust requirement accordingly. One thing I do all the time is if a client asks me to do something on the site and I can't discern what they want me to do, I will usually ask them where they go the idea. My job here is to take that nebulous response and form it into requirements. My client on the other hand, they will likely know what they want, but when it comes to describing it, they may offer a nebulous response. The way I look at it i'm the one looking at sites all day, I'm the one caught up on all the latest trends, I'm the one who knows what looks good and what doesn't. Personally I find this to be part of the Job.

#REDDIT IS SOFTWARE PRO WORLD LEGIT CODE#

No code lets people figure out that they haven't thought something out nearly as much as they think they have. I'm constantly handed shitty (or a complete lack thereof) requirements from non-technical people.

Reddit is software pro world legit