HN user

cdevs

240 karma
Posts0
Comments223
View on HN
No posts found.

Pretty cool stuff, i know ive asked for some of these features as my team uses asana for as much as we can and jira was super slow and clunky back in the day - though i checked it out recently and it seems like a much better experience.

In the tool the modals could really use a X button to close the modal, the 2 or 3 seconds i second guessed where to click each time was annoying. It would be cool to discover if asana had some of these features all of a sudden but i think putting so many features front and center is going to hurt your adoption. Slack for instances can be easily underused as simply a chat application, later on the tech guy shows up and starts dropping in chat bots and cool helpers and what not. The relationship stuff is pretty cool i hope i dig more into this stuff later.

Also are you guys planning on expanding the signup options beyond google/microsoft? it was easy for me to signup just curious how much of a roadblock that is to the rest of the internet.

I notice at my job there were a lot of i need feature x to which we commonly replied i would like to build x but the horrible old y system is stopping me or we would just make things much worse to try and meld feature x into legacy/messy y system. I was a dev dealing with the legacy systems at my company for years and then i took over management and said we need to remove or clean up these legacy weak points so we can build features faster and more maintainable, so yes we started at the first day of this year cleaning up from the worst / weakest links first on. In 6 months we are done using 2 new hires to complete new work while 2 senior devs did clean up. 6 months compared to years of spinning tires was well worth it. Eventually the CEO gets sick of hearing excuses of why we cant build this or that or are wasting 50% of our time fixing bugs. Productivity is soaring now for multiple reasons at my company, testing, documentation, removing old systems and even though we have a small team every senior dev is leading a junior dev. Side note this is the first time we have hired junior developers at this company and its been a big pay off giving a lot more free time to the senior guys to work on the most important things.

I think the ridiculous thing is every mom and pop site and blog and website needs to be gdpr compliant? insane. If the true intent was to make sure large players have their system in check then they should have simply said if you have 50,000 or more users giving you data a month or something to protect anyone interested in software from being afraid of having 2 users because now they need to read every international law. I know someone will fire back at this but what stop the United States from coming up with some law as well on the internet against how logins should be and then filing a lawsuit against every other country company that doesn’t comply. A business should follow the laws of based on the owners location and if other countries don’t like it then that’s for allies to group up and ask that minority country for change. gdpr to me is of reaching on the internet in a scary way.

Whatever your job title might be if you are the eyes and ears that generate feedback for the CEO and other management teams what are your ways of leading and guiding a lazy employee? Software developers or not it seems like as soon as everyone gets a degree they forget that we can still have toxic people in our field that slip through the hiring process and just bring everyones day down. When I say I would let someone go I mean I would suggest it and only after many attempts of me and the rest of the team trying to get through to them which seems pretty standard to me. I'd rather not work in a corporate place where I'm forced to work under or over negative people without options. Though I'm sure I come off as a typical grumpy jerk online I have to deal with being a passive aggressive person at work and I have noticed that has led to a employee or two attempting to take advantage of my hospitality and I end up working crazy hours to get things done for releases because I'm not the type of person to demand you stay late or work weekends. Everyone under me has a laid back job, I would also have a laid back job if I swapped one bad egg with a good egg or rebranded his position. I feel bad for the guys destroying work left and right while this other employee wants a red carpet laid at his feet every week to write a line of code. Maybe the 10x programmer doesn't exist but people who read about silicon valley and think free cupcakes and energy drinks should be everywhere certainly do.

This is a much longer story than I jotted down on my phone as a comment, also a tiny mutli million dollar startup but after the mostly negative comments I recieved on this post I'm starting to think there is easily a phsycological US vs THEM mentality between devs and management. I miss being able to complain, I still did the work but there was something magical about us banning together to complain about horrible management & lack of leadership. If you're going to fuss about a comment about firing and if you havent noticed some weak links at your other jobs then most likely youve been the weak link and to be fair thats fine when your job or title fits you appropriately but im talking about someone making double or triple the guy busting his butt, i was the busting his butt guy and im looking out for the rest of those guys. Theres one of many reasons I didn't go into a software job for the government.

To be honest im a passive aggressive push over, I believe in jumping in, failing early and finishing early, I asked if i could have my job back of just throwing head phones on and working but the ceo says EVERYONE is happy with me and he likes the processes im putting in place unfortunately I spend my weekday drives thinking about how to deal with a certain someone on my team who wants to act like he is ALSO manager and thats sort of why this article/blog triggered me.

We're no google but I have lead the software department on techical decisions and scaling for the past 3 years as the company/startup tripled in growth. We are a tiny power rangers sized team, I probably just have angst in my comment as there is one particular employee who was recently hired before me stepping on that goes left when I "and everyone else on the team" says go right.

I was recently a lead developer and asked to manage the team by the team. I noticed running the team can't be generalized in one size fits all, some people just want clear descriptions of projects to work and and some people want to over engineer and make a 1 day thing a 2 month job no matter how you say it should be done. Problem is how do you handle a engineer that says something can't be done in 2 hours? Well so far I have sat down with them and showed them it can be done in 2 hours, beyond that argue with me enough and I may be forced to rethink your employment. It hasn't come to that yet. most of the room follows my instructions and we are kicking butt, there's a small part of the room that wants to be dramatic about everything, their computer isn't good enough "needs 64 gigs of ram for their command line", the tools aren't good enough etc etc - basically they have management envy and that's my only struggle right now.

Restful? I thought it was dead and graphql was the new silver bullet for everything? On a serious note though this is seriously needed and I actually like the start of this API I would mind curling a device and seeing how easy it is to write 2 lines of code to email me if it dies without really having to read documentation and this is the real intent of the idea behind rest, discoverable network apis self documenting because they use links and http standards so I don't have to go look up some companies specific error codes.

Love the artwork and the work your putting into this. To be honest I'm in the middle of a graphql debate right now because our ad-hoc burger/salad endpoint said are how our API product are currently sold. Much like Burger King we don't grab cheese from a burger and put it on fries for you. This loose system does have its place but so do showing the customer a direct endpoint for burger and salad and letting them know if they want two trips they will be charged for burger and salad.

It would be scary if someone found a flaw in their API or data that exposed who went where from where everyday. It may not be stored that way but people who work at secure locations aren't allowed to bring in cell phones or workout watches but they still bring them to the parking lot showing who works where. If a flaw like this is discovered it would obviously be bad.

This seems like it would be subjective but it actually tells a story. Most likely tickets aren't being broken down enough, one employee could be snagging easy bug tickets in the morning and another employee could be working on a epic feature.

On the other side of things I have a guy at work who rocks out 20 tickets and a guy at work who tries to go into super plan mode and take his time and make sure every semicolon is perfect 20 times. This is ok, it's what management is for I need to make sure the fast guy is a little more careful sometimes and I need to check on mr planner and make sure he speeds it up sometimes.

Is her journey more for the code or the ability to create games? The artwork is pretty cool I some how assumed you took part in the art. I remember being a good doodler but lost my attention in putting to much effort into a detailed sketch. I loved games and coding but at a young age probably would have taken some of the short cuts available today. It's cool either way hope when I have a kid they are open to tech and creating something.

I'd like to see the rest of this implemented. What does this global functions look like? Are they swamped with if statements "I hope not" or are you storing some game logic in structs to replace polymorphism. I don't disagree with with the compact pawn struct as a starting point but to further prove your point I would love to see the rest / pseudo code.

On the other end of this emotional spectrum I have always loved watching games evolve with me and what you think is now the best is kids stuff compared to what comes next. Mortal kombat and doom enraged parents at the time and now the stuff we can render at 60+ frames a second would blow people away in the 80s. Part software evolution and part hardware coming together each year to push the envelope, more sprites, more triangles more pixels more frames. I can afford whatever system I want now but when I was a kid a 180$ sega was like winning the lottery.

Seems weird to put some of these languages up against each other when most of the time they are use in completely different project types games vs web vs apps vs front end vs desktop vs whatever.

I've noticed a disconnect between people we bring on the team that have a heavy oop style or do brilliant things in low level code but they lack writing code for teams fresh out of college. I remember writing magic code that did convenient abstractions for me in the background when I programmed for myself but I quickly learned this sucks when I found out someone provided me with a function that doesn't follow single responsibility in a team environment. When you work in a team write for a team, I tell everyone to write for a imaginary jr developer starting the next day who's going to read your code on day one.

Program slicing 9 years ago

I would be interested in a source code scanner that tells you how many functions or lines can modify a variable and show a table of variables/counts. This could be helpful on a new small codebase or checking variables in a specific ugly class that always has scope errors so we can tell our bosses it sucks.

Woah, my story is almost the same as yours except I started out in iOS games and what not at about 27 compare to your 25 then moved to backend stuff around 30 to get away from being stuck in Apple only world and now I'm managing a 10 person team at 34 for a multi million dollar website after being a key player in scaling them up beyond any thing possible before I got there. 27 years old wasn't exactly a clean start at programming for me though I was buying books on it since I was 12 "c,c++,java" not that I always understood pointers much until I really dug into building things with iOS but like I said that was a bit of tunnel vision for my future, go full stack and read about everything all the time.

I did a year of community college courses and all but 2 of them were online. In person I hated 19 year olds wasting class time that I've paid for and loved being able to push forward online on my time. I would be interested in finishing up online, spare me the social interaction / frustration. That's my take on things and may not fit everyone but I see a end to the expensive roadblock as more education goes online.

Agree, I think code review also helps yank out that laziness in that code that we thought we didn't have time to make more readable. Send the code back and make them push their code to a better level before putting it live. I've noticed UX problems in code reviews from people who should know better, we just get lazy and think "working" is good enough.

Spread your knowledge around, read on oop, read on functional programming, learn what google and Facebook do in a situation, learn to get good enough to criticize with confidence. If you can't criticize a situation with confidence then learn more about it.