Hacker Newsnew | past | comments | ask | show | jobs | submit | FuzzyDunlop's commentslogin

This already happens on Giff-Gaff (a mobile network) and is opt-out only. It's not uncommon to find out a security-related blog on the front page of HN is blocked by the filter, and sites for projects like Metasploit are also blocked.

It's silly.


All mobile networks have this censorship, but it was easy to opt out of, and the censorship is very sloppily implemented (for me, changing DNS servers or using any trivial proxy bypassed it before I opted out).


There's a startling lack of empathy here. Overcoming feelings of isolation and trying to get more involved is easier said than done for some, and the whole concept of taking something by the horns and just fucking dealing with it, or offering advice by 'telling it like it is' is astonishingly unhelpful to anyone who feels upset or down because of something. Not just sexism, or isolation, but depression, anxiety, loneliness, and all manner of things which will cause a person to feel like they're on the outside looking in, or beyond reproach.

The entire post cries out for such an empathetic response and I'm not surprised in the slightest that none is forthcoming in this thread.

I've had experiences myself relating to this attitude to things, and know that posts like this are incredibly difficult to write, and the emotions are difficult to discuss. I'm glad the author found the courage to publish it.


I'm not trying to say that she should "just deal with it". These are legitimate feelings and struggles, but they have nothing to do with sexism. Her attributing these problems and feelings to sexism prevents any actual discussion of how to effectively address these feelings because that's sexist, obviously she plays no role in this if it's because of her gender.

She's victimizing herself, and by association all of the other women in tech who only work with men. Honestly, I'm a bit defensive here because I'm tired of being told by other women that any problem I encounter at work is because of my gender.

Getting involved is hard, and takes practice. Same goes for mentoring others. Had she simply wrote about those struggles, the comments would be filled with similar anecdotes and empathy from all the people in HN who have been there regardless of gender.

But claiming all of these feelings are because of her gender is, well, sexist.


It sounds like you are so defensive that you're not willing to recognise that any problems could be because of their gender, which is just as likely to be wrong as the people who insist that all problems are because of gender. How do you know that she wasn't a perfectly capable lead with team members who didn't take her seriously because she was female? Do you literally believe that's an impossible scenario?

From the article, while I can't judge her abilities as a lead, at least part of her problems were to do with feeling like she was being treated differently because she was a woman and having no way to verify this. If she was one of a number of women, then it would be much easier for her to check on that feeling and see if it was true. When you are the only one of your kind, you can't look for people with similar backgrounds to look for correlations, so you can't really tell if there is a pattern or not. If I thought that it was completely unrealistic and impossible for any developers to be sexist, then I might write this story off as entirely her own neuroses - but I am not convinced that is the case.

(also, given the numerous comments along the lines of 'you don't like assholes well get out of tech then', I suspect she would have hit pushback no matter how she phrased any stories of struggles with dealing with assholes)


Sounds elitist. The only crime the author would have committed there is choosing a linkbaity title for their post, because something like that could cover any amount of interesting topics.

"Understanding Go and Coroutines as a PHP developer" for example might be useful, and it wouldn't suffer from being written by someone who hadn't absorbed the living spirit of Rob Pike before they wrote it.


If preferring to learn a subject from someone who knows it well (and has spent days or weeks rather than minutes editing their prose) makes me an elitist, then fine, I'm an elitist.

Your hypothetical article about Go and coroutines could be very useful, provided that the author has had some significant experience with both Go and PHP (e.g, they've written and maintained non-trivial programs in both languages). Otherwise, it's likely to be full of misconceptions and even errors.


It's handy unless you accidentally start searching for anything that could be mistaken for an IP address or domain. Typing in `0x10c` to find the site for the game, or `minimal-library.js`, or whatever, won't take you to a search results page.

Works alright for most things though, and I think it's still better than Google's default to Google approach, which is frustrating when you're working on a locally hosted site and keep getting sent to a search page.


Since Adobe requires you to register before you can download one of their trials, I'd wager that a lot of them are completely throwaway, or just lifted from bugmenot or whatever.


You can do Rails to a fair extent without really knowing Ruby, and just fumbling through it with a bunch of gems and messy code. In some ways it can be the gateway to learning Ruby itself, if you were so inclined to do so.

For things like CoffeeScript, which are fairly thin layers over another language, I'd always advise to just learn JS first. Dart and Clojurescript though are so far removed from their compilation target that you don't really need to know the JS, as long as there's good library support for what you want to do. In the case of clojurescript the interop is so seamless that it puts the focus on learning the APIs, which is where the true complexity lies. Of course, and even more so with typing, you also have the compiler to back you up.


Anecdotal, but there have been a number of times I've clicked a result on Google, and have been unable to get back to the results page without either double clicking the back button or finding it in the history. You'd just go to the original page that redirects you to the actual content and get stuck in a loop.


It doesn't feel like it's enterprise enough to be realistic.

    class TwoBaconRashersInsideTwoSlicesOfBreadFactory {
      
      /* Make a sandwich
       * <p>
       * Construct a foodstuff consisting of two slices 
       * of bread with two slices of bacon.
       * @return TwoBaconRashersInsideTwoSlicesOfBread a sandwich
       */
      Public TwoBaconRashersInsideTwoSlicesOfBread getSandwich () {
       BaconRasherFactory pig = new BaconRasherFactory();

       BaconRasherInstance bacon1 = pig.getBaconRasher();
       BaconRasherInstance bacon2 = pig.getBaconRasher();


       SliceOfBreadFactory loaf = new SliceOfBreadFactory();
       
       SliceOfBread bread1 = loaf.getSliceOfBread();
       SliceOfBread bread2 = loaf.getSliceOfBread();

       return new TwoBaconRashersInsideTwoSlicesOfBread(bread1, bacon1, bacon2, bread2); 
    }
Or something... trying to do Enterprise Java is hard.


You can always use this gem for reference:

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...


Not enterprise enough, it doesn't implement any interfaces nor extends any generic classes, there also should be some try/catch blocks (what if the bacon isn't fried enough?) and of course several unit tests to guarantee the highest quality sandwich ;)


There isn't even any XML. Not enterprise at all, by definition.


Yeah, we should be able to define types of sandwiches in XML.

What if someone wants a BLT?


Language bashing is what characterizes our industry.

I have the dream that one day we will recognize languages as the tool they are and be mature enough to chose tools by utility and not by hype, hipness or pop culture and see there benefits and limitations.


I have the dream that one day we will recognize languages as the tool they are

We do. They're just terrible tools. Do you think other industries don't criticize their tools? Hell, they have full magazines and reports reviewing and grading them.

The idea that all languages/tools are created equal and just have different use cases is nonsense.


Criticizing tools is excellent. Deciding about their benefits and limitations, learning about when to use them and when not to use them. Sharing experiences so people can make better choices.

Criticism in this way is rare though. Bashing a language to be cool, be part of the hip crowd, make you feel better about your own choices, bashing languages for karma or laughs, bashing languages you have no experience in comparing it with a language you've used for some weeks is not criticism.

Does it help others? If it does, it is criticism. If it doesn't and only makes you feel good after posting, it's not.

[Edit] And the really sad part is that people make language arguments into people arguments, stereotyping people to make themselves feel better.


>learning about when to use them and when not to use them.

Learning never to use them is just as legitimate.

"A place for everything and everything in its place" isn't a law of physics, it's a battle-cry for the obsessive compulsive.


"Learning never to use them is just as legitimate."

Indeed! I would from my experience not use Z80 assembler - though I like it much more than 6502 - and CP/M as an OS for a social media website.

I have the gut feeling though that your comment might be about Java, which might not be warranted. The last company I've worked for makes >$200M in profit a year and will be sold soon for >$1b - based on a Java platform. The next company I worked for was skyrocketing and sold for $200M - based on a Java platform. Both profited from good performance, stability and GC maturity during high periods of growth and load and a good pool of developers during peak hiring times.

But then we might differ in our goals and evaluation criteria, mine is about getting things done to support a business in a sustainable way.


He is not bashing Java per SE but a special kind of Java: Enterprise Java and IMO that deserves a bashing on general principle. Enterprise Java just never seems appropriate.


I don't know if that pun was intentional, but if it was it's absolutely fantastic.

So as to remain on topic: I agree with you but the other side of the coin is that Java the language can't seem to live down Java EE and its culture. It's trying, though. I give particular kudos to the Clojure and Scala communities for helping to rebrand the JVM as something awesome independent of Java. That helped me, at least, to realize that I shouldn't conflate the two in my head.

The only stumbling block I have to get around in my head now when I think JVM is "JVM == long startup times", which is still kinda true but nowhere near as bad as it was.


He was bashing a programming language - you call it Enterprise Java - for laughs and karma, not seeing languages as tools you can use based on your judgement. I hope we once will grow beyond bashing.

[Edit] And this is the highest voted comment on a thread about how cool GTA V is to include programming references and how deep their open world is.


HN youngers of today like to bash Enterprise Java, whereas the old guys already have their share of scares from:

Enterprise Clipper

Enterprise C

Enterprise C++

Enterprise Perl

Enterprise TCL

Enterprise insert language here

You just need to let the enterprise architects loose...


I'm probably young enough to have experienced Enterprise PHP, which by all accounts (at least when Symfony2 was just released) seemed like the love-child of Enterprise C++ and Enterprise Java.


But how will some define their superiority? By not using semi-colons?


Hmm... how about...

@Service public class SandwichFactoryImpl implements SandwichFactory {

	    @Autowired
	    public EmptySandwichFactory emptySandwichFactory;

	    @Autowired
	    public FoodComponentFactoryFactory foodComponentFactoryFactory;

	    @Override
	    public Sandwich makeSandwich(Collection<FoodComponentDescription> foodComponentDescriptions) {

	        Sandwich sandwich = emptySandwichFactory.newSandwich();

	        for (FoodComponentDescription foodComponentDescription : foodComponentDescriptions) {
	            FoodComponentFactory foodFactory = foodComponentFactoryFactory.getFactory(foodComponentDescription.getType());

	            for (int i = 0; i < foodComponentDescription.getQuantity(); i++) {
	            	sandwich.addFood(foodFactory.create());
	            }
	        }
	        
	        return sandwich;
	    }

	    public SandwichDTO makeMyFavoriteSandwich() {
	        Collection<FoodComponentDescription> components = Lists.newArrayList();

	        components.add(new FoodComponentDescription(FoodType.BREAD, 1));
	        components.add(new FoodComponentDescription(FoodType.BACON, 2));
	        components.add(new FoodComponentDescription(FoodType.BREAD, 1));

	        return makeSandwich(components);
	    }

	}


This is much more inspired. I sort of feel sympathetic, because of the potential mental anguish you were likely to have incurred while writing it.


Your use of "new" implies those factories have no interfaces. Normally they would be injected.


Make the comment into Javadoc, add some more modifiers, increase the method names and I think you're well on your way.


Any language has hard time being enterprise.

That what the space station architects are there for.


You can't renew your fingerprint, though.


There are many 'beers' in existence which, for all that they taste like, might as well be the product of a human civet.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: