71–80 of 242 posts
In 2017 (or from this week :)), I am looking to hire 5 Sr. Dev/Cloud Ops Engineers, with competency in AWS (CloudFormation, IAM, etc), Azure, Chef, Terraform, general Ops. PM for more info.
You sound like a very cynical, older person. I'm interested to hear your story and why you have developed strong views on things that make a pretty small difference in the grand scheme of things. Any bad experiences that we could learn from? Thanks in advance. Edit: I'm not trolling, sorry if my post sounds insincere. If there's a good fucking story behind your statements, I want to hear it.
IMO somewhat uninformed opinion (longtime dev on two of the biggest platforms, played a bit with node etc a few times) the Javascript ecosystem has seems to have numerous issues. Here is my impression:
- being equally bad or worse than php in a number of ways (I used to write php, the right way ; )
-to: having bad dependency management
-to: the complete ecosystem being in a churn, always. Like if php constantly was having the php4-5 transition or if python 2 and 3 was simultaneously in a flux.
-to: being pushed for the wrong reasons
Same goes for gradle (and I guess a number of other hip technologies):
I start looking into it and it turns out it isn't even faster! The unique selling point of gradle seems to be that it is not xml-based or something.
Thanks but no thanks. Not interested.
In fact just yesterday I commented on something and said: sounds cool so I will avoid it for now. I'll use the old way, get it done and then add it on a rainy day (or better: a rainy night) after funding is ok or whatever.
Edit to match your edit:
I have replied as well as I could. I didn't even notice it was you until I had posted.
That said I think you make your own life worse by referring to others as "cynical, older person" and stating without doubt that some "... things that make a pretty small difference in the grand scheme of things" - especially that latest part makes it look like you have already made up your mind.
Oh, and as I mentioned last time: I'd stop swearing here, at least for small stuff like this ;-)
We hope to expand our team in early 2016 and have a mainly java micro-services with some PHP and native apps on the front. Will likely add to the java team in addition to an IOS dev.
Nice atmosphere, nice people. We try to select for people who don't like to be micromanaged (but are still friendly) and assign responsibility not tasks wherever able. Varying degrees of success but overall happy with the approach.
Looking for at least one highly skilled person with java experience and ideally a fin-tech background. Not sure the salary would be competitive with SF but cost of living is small and its a great lifestyle (for those who like daily excitement/challenges and learning new cultures). On site. Other roles would likely be unsuitable (read: cheap!) for the HN audience.
Intelligence. Tenacity. Ambition. Judgement. Bonus points for recognizing the bullshit parade that is the current startup world. e.g.: NodeJS has value, but it's mostly the same wheel we've had for 20+ years. Or that MongoDB's changelog has consisted of standard SQL features for the past five years and that pgsql would have been just fine (had people read some boyce-codd anyhow).
Funny, because it's pgsql that added a JSON data type in response to MongoDB and others.
You sound like a very cynical, older person. I'm interested to hear your story and why you have developed strong views on things that make a pretty small difference in the grand scheme of things. Any bad experiences that we could learn from? Thanks in advance. Edit: I'm not trolling, sorry if my post sounds insincere. If there's a good fucking story behind your statements, I want to hear it.
Not op, but: IMO somewhat uninformed opinion (longtime dev on two of the biggest platforms, played a bit with node etc a few times) the Javascript ecosystem has seems to have numerous issues. Here is my impression: - being equally bad or worse than php in a number of ways (I used to write php, the right way ; ) -to: having bad dependency management -to: the complete ecosystem being in a churn, always. Like if php con…
I use node.js, but doing things the "node.js" way is just crazy. You don't make a higher level project depend on a package manager
I am 100% owner of an internet company making 7 figure profits annually. I am extremely secretive of my business, almost to the point that some would consider a pathology. However, I will divulge my hiring strategy, because even if everyone uses my method, there will still be many employees for me to choose from. I look to hire people who just need a job. People who are qualified, but not overly qualified. People I k…
You sound like a very cynical, older person. I'm interested to hear your story and why you have developed strong views on things that make a pretty small difference in the grand scheme of things. Any bad experiences that we could learn from? Thanks in advance. Edit: I'm not trolling, sorry if my post sounds insincere. If there's a good fucking story behind your statements, I want to hear it.
Not op, but: IMO somewhat uninformed opinion (longtime dev on two of the biggest platforms, played a bit with node etc a few times) the Javascript ecosystem has seems to have numerous issues. Here is my impression: - being equally bad or worse than php in a number of ways (I used to write php, the right way ; ) -to: having bad dependency management -to: the complete ecosystem being in a churn, always. Like if php con…
"Sounds cool so I will avoid it for now, I'll use the old way, get it done and then have fun with it after we solve the problem"
I actually feel that there's some great advice here. I mean, great "fucking" advice. People in my community tend to jump into things that are new and shiny, and it makes me feel that I'm missing out sometimes, or that my tools aren't good anymore. Oh, React is out and is past .1? Time to change my entire coding style. I guess if you are familiar with a way of doing something that works, get it done that way, then improve it later.
Regarding your other advice -- I'd rather call people "old and cynical" and give them a chance to show me why I'm wrong. Otherwise, I'd just stay wrong. I'm actually glad that you take the time to try and help people like that, I think I'd get along well with you had I known you in person.
On the frontend side of things I'm looking less for specific framework experience and more for overall programming competency. JavaScript development moves so fast now that it really doesn't make sense to scope your hiring to angular, react, etc.
Earlier quoted context omitted.
The question was what tech skills will you be hiring for and your answer was essentially I just want a plodder who's not overly smart and won't question my authority. Sound about right?
Tech skills are only one dimension of a multidimensional process that employers like me use to make decisions. I am here to offer contrarian advice that might be helpful to someone early in his career who might be a great programmer but may also be dismayed because he thinks the only path to a successful tech career is devoting your life to your job or going to an ivy league school and I am here to say that is not th…
How would is such a person define success for themselves, and how does your prescribed plan achieve that?
In other words, are you prescribing a plan that is beneficial for the company, but bad long-term for the employee, because they didn't grow enough by not 'devoting their life to their job'?